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

@weftjs/compiler

v0.1.6

Published

TSX to Template IR, with effect inference and escape elision.

Downloads

1,270

Readme

@weftjs/compiler

TSX to Template IR, with effect inference and a type-driven escape class.

Part of weft, a TypeScript fullstack framework that negotiates the wire form of a piece of UI per request. weft build and weft dev run this for you.

npm install @weftjs/compiler

What it is

A fragment body is a declaration the compiler reads and never runs. That is the line the design will not move, and it is what makes the rest possible: there is nowhere for a call to happen, so the client bundle cannot grow with the application.

The compiler parses with Oxc, seals each fragment into IR, and infers what it reads. The cache class is derived from those reads, which is why there is no setter for a cache key anywhere in the framework — a key you can hand-write is a key that can disagree with the code. .cache('public') on a fragment that reads identity fails the build with identity named.

Refusals are named and explained rather than silent: E_BRANCH_ON_SIGNAL, E_CHILDREN_NOT_SOLE_CHILD, E_COMPONENT_NOT_SINGLE_ROOT and the rest are each a consequence of templates being data compiled without seeing their call site.

Reference

License

MIT