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

@openstatus/health-nats

v0.1.4

Published

NATS probe for @openstatus/health

Readme

@openstatus/health-nats

NATS probe for @openstatus/health. Flushes a NatsConnection — one PING / PONG round trip with the server — and fails the check when the server does not answer or the connection has been closed.

deno add jsr:@openstatus/health jsr:@openstatus/health-nats
npm install @openstatus/health @openstatus/health-nats
import { connect } from "@nats-io/transport-node";
import { createHealthHandler } from "@openstatus/health";
import { natsProbe } from "@openstatus/health-nats";

const nc = await connect({ servers: env.NATS_URL });

Deno.serve(
  createHealthHandler({ probes: [natsProbe({ connection: nc })] }),
);

Reuse the connection your application already holds: NATS clients keep one multiplexed connection per process and reconnect on their own, so the probe reports what your publishers and subscribers actually see. While the client is reconnecting, flush() waits until the server is back — set timeoutMs to bound that. Any of the official clients works: @nats-io/transport-node, @nats-io/transport-deno, the websocket transport and the legacy nats package all expose the same flush() and isClosed().

natsProbe({
  connection: nc,
  // optional overrides from the Probe contract
  name: "events",
  critical: true,
  timeoutMs: 1000,
  skip: () => env.NATS_URL == null,
});

Non-critical by default: messaging usually carries background work, so an outage degrades the report instead of taking the service out of rotation. Set critical: true when requests cannot complete without publishing.

The connection is typed structurally as { flush(), isClosed?() }, so the NATS packages are optional peer dependencies for their types only and the probe adds no runtime import of them. The factory throws ProbeConfigError at construction when the connection has no flush().

About openstatus

openstatus is the open-source uptime monitoring and status page platform. This package is part of @openstatus/health, the /health endpoints behind openstatus's own services, extracted so any JavaScript server can expose one. Point an openstatus monitor at the endpoint and assert on status in the body to be alerted on degraded before it becomes unhealthy.

Source: github.com/openstatusHQ/health. Issues and PRs welcome.

License

MIT