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/server

v0.4.0

Published

Fetch-API request handlers for the CHIL token exchange. Runs on Node, Workers, Deno and Bun.

Downloads

226

Readme

@chiljs/server

Fetch-API request handlers for CHIL. (Request) => Response | null, so it runs on Node, Workers, Deno and Bun, and returns null for paths it does not own so it mounts in front of your router.

import { createBroker } from '@chiljs/core';
import { createHandler, createMintHandler } from '@chiljs/server';
import { toNodeHandler } from '@chiljs/server/node';

const exchange = toNodeHandler(createHandler({ broker, sink }));

createServer(async (req, res) => {
  if (await exchange(req, res)) return;
  ...your routes
});

Three public routes under basePath (default /chil): GET /check, POST /claim, POST /upload. All three are unauthenticated by design — the token is the credential.

createMintHandler is separate and must not be public. It issues credentials; it takes a room resolver so authentication is impossible to forget.

The sink

The one piece you write. store(ctx, body) receives a ReadableStream already capped at maxBytes and already past your inspect allowlist. Let BodyRejected propagate, and clean up partial writes in a finally.

ctx never contains the token: the authoriser has no business in the layer that writes to disk.

Full documentation: the repository README.

MIT.