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

@bosejs/compiler

v0.2.1

Published

The 'Brain' of Bose framework. Handles closure extraction and resumability shredding.

Readme

@bosejs/compiler

The Babel plugin that powers Bosejs — extracts $() closures into lazy resumable chunks.

What it does

The compiler is the "brain" of Bosejs. It transforms your source files at build time:

  1. Finds every $() closure in your component code
  2. Extracts it into its own standalone JS chunk file
  3. Replaces it with a reference object { chunk: 'chunk_abc123.js' }
  4. Injects a stable signal ID so the runtime can sync state on resumption

The result: your page ships with zero JS. Chunks are fetched lazily on first user interaction.

Install

This package is installed automatically when you install @bosejs/core. You don't need to install it directly.

npm install @bosejs/core   # pulls in @bosejs/compiler automatically

How $() works

You write:

const increment = $(() => {
  count.value++;
});

The compiler outputs (in your page):

const increment = { chunk: 'chunk_a1b2c3d4e.js', props: [] };

And creates public/chunks/chunk_a1b2c3d4e.js:

// Lazily fetched only when the user first clicks
const { count } = __BOSE_STATE__;
count.value++;

Chunk IDs are deterministic (based on file content hash) — the same source always produces the same chunk ID across builds.

License

MIT © Bosejs Contributors