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/redis-stream

v0.5.0

Published

Redis Streams Publisher/Subscriber for @millstream on ioredis: XREADGROUP consumer groups, XACK on ack, XAUTOCLAIM recovery

Readme

@millstream/redis-stream

Redis Streams Publisher / Subscriber for millstream, built on ioredis. Peer dependency: ioredis@^5 || ^6; Redis ≥ 6.2 (XAUTOCLAIM).

import { Redis } from 'ioredis';
import { RedisStreamPublisher, RedisStreamSubscriber } from '@millstream/redis-stream';

const client = new Redis('redis://localhost:6379');
const publisher = new RedisStreamPublisher({ client, maxLen: 100_000 });

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

The client belongs to you. Each subscription opens a duplicate() of it for blocking reads.

Semantics

  • Topic = stream key (streamName to change). publish() is one XADD per message inside a MULTI, with fields uuid, payload (binary-safe) and metadata (JSON). maxLen trims the stream (MAXLEN ~ n) — trimmed entries are gone even for groups that haven't read them.
  • consumerGroup → XREADGROUP: each group gets every message, subscribers of one group compete for them, and progress lives in Redis. New groups start at startId ('0': everything, default; '$': only new entries).
  • No group → XREAD from startId with the position in memory: every subscription sees the whole stream.
  • Ack → XACK. Nack → in-place redelivery of a fresh copy after nackResendMs (the entry stays pending), so a poison message blocks its subscription: add poisonQueue / retry middlewares on the Router.
  • Ordering: strict with concurrency: 1 and one consumer per group. concurrency: n handles up to n entries in parallel.
  • Crashes: entries pending on a dead consumer for claimIdleMs (30s) are claimed with XAUTOCLAIM by the group's other subscribers (checked every claimIntervalMs), which can reorder them. Entries being handled have their idle time reset, so slow handlers aren't claimed. Abort while holding an entry makes it claimable at once.
  • A subscription's consumer (millstream-<uuid>, or consumerName) is removed from the group when it stops with nothing pending.
  • redisStreamInfo(msg) returns stream / entry id / group. Entries added by other clients get the uuid redis:<stream>:<id>, and their fields (as JSON) as the payload.