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

@chiljs/core

v0.4.0

Published

Protocol, token broker and store contract for CHIL, a single-use token handoff. Zero dependencies, isomorphic.

Downloads

289

Readme

@chiljs/core

Protocol, token broker and store contract for CHIL. Isomorphic, zero dependencies — it runs in a browser, in a Worker and on Node.

import { createBroker, memoryStore, parseToken } from "@chiljs/core";

const broker = createBroker({ store: memoryStore(), ttlMs: 5 * 60 * 1000 });

const { token, flow } = await broker.mint("shop-1"); // behind YOUR auth
const { room, secret } = parseToken(token)!;

await broker.check(room, secret); // never consumes, safe to poll
await broker.claim(room, secret, claimantId); // first browser wins
await broker.consume(secret); // only after the file is stored

Most applications reach for @chiljs/server instead, which wraps this in request handlers. Use this package directly when you want the four operations and none of the routing.

Writing a store

memoryStore() is the default and is correct for a single process. Anything else must make claim and consume atomic — see the note on TokenStore, and run the suite:

import { checkStore } from "@chiljs/core/conformance";
const failures = (await checkStore(() => myStore())).filter((o) => !o.ok);

Full documentation: the repository README.

MIT.