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

@millstream/nats

v0.5.0

Published

NATS JetStream Publisher/Subscriber for @millstream: Nats-Msg-Id dedup, durable consumers as consumer groups, ack/nak with delay

Readme

@millstream/nats

NATS JetStream Publisher / Subscriber for millstream, built on the @nats-io/* v3 modules. Peer dependencies: @nats-io/jetstream@^3, @nats-io/nats-core@^3 (plus a transport such as @nats-io/transport-node to connect).

import { connect } from '@nats-io/transport-node';
import { NatsPublisher, NatsSubscriber } from '@millstream/nats';

const connection = await connect({ servers: 'localhost:4222' });
const publisher = new NatsPublisher({ connection });

router.addConsumerHandler({
  name: 'billing',
  subscribeTopic: 'orders.created',
  subscriber: new NatsSubscriber({ connection, consumerGroup: 'billing' }),
  handler: async (msg) => {
    /* … */
  },
});

The connection belongs to you: close() doesn't close it.

Streams and consumers

  • Topic = subject. By default each topic gets its own stream named after it (orders.created → orders_created, created on first use with subjects: [topic], like Watermill's AutoProvision). autoProvision: (topic) => ({ max_age, num_replicas, … }) adds stream settings. With streams managed elsewhere (one ORDERS stream for orders.>), pass stream: () => 'ORDERS' and autoProvision: false.
  • consumerGroup → a durable pull consumer <group>_<topic> (durableName to change). Each group gets every message; subscribers of one group compete for them; progress survives restarts. A durable consumer created earlier with other settings (e.g. a new concurrency) is updated.
  • No group → an ephemeral consumer per subscribe() that starts at the beginning of the stream (deliverPolicy: 'new' to only get new messages), deleted when the subscription ends.

Semantics

  • Publish waits for every PubAck. Nats-Msg-Id = msg.uuid, so the stream drops a re-published message within its duplicate_window (2 min by default) — a forwarder retrying after a crash doesn't duplicate. Metadata = headers.
  • Ack → +ACK, confirmed by the server (ackAck). Nack → -NAK with a nackResendMs delay (default 100ms). consumerConfig: { max_deliver, backoff } hands retries to JetStream instead.
  • Ordering: max_ack_pending = concurrency, so with the default concurrency: 1 a consumer is strictly ordered and holds the next message until the current one is acked.
  • Long handlers: the server redelivers a message not acked within ackWaitMs (30s). Held messages are kept alive with working(), so this only matters when a process dies.
  • Abort while holding a message → -NAK right away (redelivered to the group's next subscriber).
  • natsInfo(msg) returns stream / stream sequence / delivery count. Messages published without an id get a deterministic uuid nats:<stream>:<seq>. Set uuidHeader: WATERMILL_UUID_HEADER to exchange messages with Go Watermill services.