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

@lunibee/sharding

v0.4.0

Published

> Run many gateway shards in one process (`ShardManager`), across child processes > (`ClusterManager`), and message between them (`ShardBus`).

Readme

@lunibee/sharding

Run many gateway shards in one process (ShardManager), across child processes (ClusterManager), and message between them (ShardBus).

bun add @lunibee/sharding
import { ShardManager, ShardBus } from "@lunibee/sharding";
import { GatewayIntentBits } from "@lunibee/types";

const manager = new ShardManager({
    token: process.env.DISCORD_TOKEN!,
    intents: [GatewayIntentBits.Guilds],
    shardCount: "auto", // Discord's recommended count
});
await manager.connect(); // starts shards 5 s apart (spawnDelay)
console.log(manager.getShardIdForGuild("123456789012345678"));

const bus = new ShardBus(0, "my-bot");
bus.respond("guildCount", () => 42);
bus.onError((error, message) => console.error(message.type, error));
const replies = await bus.broadcastRequest<number>("guildCount", null, {
    expected: 3,
    timeoutMs: 5_000,
});
console.log(replies.reduce((sum, reply) => sum + (reply.result ?? 0), 0));

What's inside

  • ShardManager: one Gateway per shard, IDENTIFY pacing, optional auto-scaling (autoScaleInterval), getShardIdForGuild(), destroy().
  • ClusterManager: orchestrates cluster processes (child_process.fork, Node and Bun). It assigns shards deterministically (SHARD_LIST, SHARD_COUNT, CLUSTER_ID, CLUSTER_COUNT env vars; a worker cannot start the fleet again), hands out IDENTIFY slots across all clusters, waits for readiness (ready(), waitForReady, startTimeout), restarts crashed clusters with backoff, routes request() / broadcast() / requestCluster() to the owning cluster, reports health(), and can move a failed cluster's shards to another cluster (reassignOnGiveUp). With remote, it is a coordinator for ClusterHost agents on other machines (authenticated WebSocket, fenced workers). Inside a worker, ShardManager owns only the cluster's shards and uses the parent for IDENTIFY.
  • ShardBus: send, broadcast, on/off, onError, and request/reply with respond, request and broadcastRequest. Shards query each other without evaluating received code.

What's new in 0.2.0

Startup in rounds of max_concurrency paced by sent IDENTIFYs (maxConcurrency, handshakeTimeout), a session-start-limit check that keeps live shards, fetchGatewayInfo() and health().

Docs: https://lunibee.js.org/core-concepts/sharding/

What's new in 0.3.1

ShardManager and ClusterManager work as one system: one worker contract, one IPC channel, one IDENTIFY authority, typed events, requests with timeouts, health and recovery. See https://lunibee.js.org/core-concepts/sharding/ and examples/cluster.