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

@openknot-ts/knot-rest-fastify

v0.0.6-preview

Published

Serves OpenKnot REST routes on the Fastify host.

Readme

@openknot-ts/knot-rest-fastify

Serves @openknot-ts/knot-rest routes on the Fastify host. The router and the selected route sets join through its requirements.

Usage

import { fastifyHttp } from "@openknot-ts/fastify-server";
import { restFastify } from "@openknot-ts/knot-rest-fastify";
import { defineApplication } from "@openknot-ts/wire";

export const application = defineApplication({ modules: [behavior, flow, io, transport, fastifyHttp, restFastify] });

API

| Export | Description | | --- | --- | | restFastify | Ready module: joins the host's fastifyPlugins collection. | | fastifyRestPlugin({ requirements?, maxBodySize? }) | The same with a body limit from the application's own config, which replaces REST_MAX_BODY_SIZE. |

Behavior

  • Registers one catch-all route in its own encapsulated scope, so routes of other plugins (tRPC, health) take precedence; the router answers 404 and 405 for the rest.
  • That scope leaves the request stream unread: the router reads a body only for routes that take one, through readJsonBody, with application/json and REST_MAX_BODY_SIZE. 413 and 415 close the connection. Fastify's bodyLimit applies to the other plugins only.
  • Responses go through Fastify's reply, so its hooks run.
  • The request's signal aborts when the response closes early; a stopping host still answers what it admitted.

Custom configuration

const plugin = fastifyRestPlugin({
  requirements: { settings },
  maxBodySize: ({ settings }) => settings.API_BODY_LIMIT,
});
// modules: [..., fastifyHttp, providePlugs([plugin])] instead of restFastify

Example and tests

pnpm --filter @openknot-ts/knot-rest-fastify example

test/fastify.test.ts runs on a real host: status codes, limits, a client disconnect that leaves no published or retained work, and a request admitted before stop that is still answered.