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-health

v0.0.6-preview

Published

Health probe HTTP adapters for the OpenKnot Node and Fastify hosts, and the probe routing other hosts share.

Readme

@openknot-ts/knot-health

Serves the @openknot-ts/health probes over HTTP: as middleware for the Node host and as a plugin for the Fastify host. It owns probe routing, framing and paths; the host owns listening, the health core owns the probe semantics.

Usage

import { healthHttp } from "@openknot-ts/knot-health";
import { http } from "@openknot-ts/knot-http-node";
import { trpcHttp } from "@openknot-ts/trpc-knot-server-handler";
import { defineApplication } from "@openknot-ts/wire";

export const application = defineApplication({
  modules: [applicationModule, transport, http, trpcHttp, healthHttp],
});

On Fastify, use the module of the same name from /fastify:

import { fastifyHttp } from "@openknot-ts/fastify-server";
import { healthHttp } from "@openknot-ts/knot-health/fastify";

export const application = defineApplication({ modules: [applicationModule, fastifyHttp, healthHttp] });

The Bun host uses @openknot-ts/knot-health-bun. Selecting the health core alone adds no endpoints.

API

| Entry | Export | Description | | --- | --- | --- | | @openknot-ts/knot-health | healthHttp | Ready Node module: probe middleware before the application handler. | | | nodeHealthMiddleware({ requirements?, paths? }) | Node middleware with custom paths. | | | healthHttpConfig | The default path configuration. | | @openknot-ts/knot-health/fastify | healthHttp, fastifyHealthPlugin({ requirements?, paths? }) | The same for the Fastify host. | | @openknot-ts/knot-health/probes | probeSettings, ProbePaths, ProbeOptions | Host-neutral routing, configuration and framing for other host adapters. |

Configuration

| Variable | Default | Probe | | --- | --- | --- | | HTTP_LIVENESS_PATH | /livez | Liveness | | HTTP_READINESS_PATH | /readyz | Readiness | | HTTP_HEALTH_PATH | /health | Readiness plus dependency checks |

Paths must start with / and differ; invalid or duplicate paths fail before the host listens. paths(dependencies) returns { liveness, readiness, health } from the application's own config and replaces these variables entirely.

Responses

  • GET and HEAD answer 200 when up, 503 when down, with Cache-Control: no-store and the body { "status": "up" | "down" } (none for HEAD). Query strings do not affect matching.
  • Other paths and methods pass to the application unchanged.
  • A closed request aborts the dependency checks' signal.
  • Readiness is down during startup and from the moment the application starts stopping; a failing dependency affects only /health.

Tests

test/probes.test.ts covers lifecycle phases, dependency failures, HEAD, cancellation and paths; test/config.test.ts custom paths; test/fastify.test.ts the Fastify plugin. Both main examples select the Node adapter.