npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@opentf/web

v0.24.0

Published

The native-first OTF Web runtime — signal-based reactivity and zero-VDOM DOM operations, paired with the IR-based compiler.

Readme

@opentf/web

The native-first OTF Web runtime — signal-based reactivity and zero-VDOM DOM operations, paired with the IR-based compiler (@opentf/web-compiler).

You normally don't call this API by hand. You write .jsx components; the compiler lowers them to plain DOM code that imports its helpers (signal, computed, bindText, bindList, …) from this package. Components compile to self-registering web-* Custom Elements.

Installation

bun add @opentf/web

Scaffold a ready-to-run app with @opentf/create-web and drive it with @opentf/web-cli.

What's inside

  • Reactivity — a from-scratch signal / computed / effect core.
  • DOM runtime — fine-grained bindings (bindText, bindAttr, bindList, bindChild, setProp, spread, clsx) the compiler targets, plus Context, Portal, ErrorBoundary, and event dispatch (emit).
  • Compiler macros — authored in your components, resolved at compile time: $state, $derived, $ref, $context, $effect, $expose, and the onMount / onCleanup / onResize / onVisibilityChange / onMediaQuery lifecycle hooks.
  • <Link> — client-side navigation, shipped as JSX source and compiled by your app's pipeline.

Entry points

| Import | Contents | | --- | --- | | @opentf/web | runtime + reactivity + Link (what compiled components import) | | @opentf/web/signals | the reactivity core on its own | | @opentf/web/runtime | DOM helpers, Context, Portal, ErrorBoundary | | @opentf/web/server | string-composed render helpers for SSG |

License

MIT © Open Tech Foundation