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

@whisperr/node

v0.1.2

Published

Whisperr Node SDK — reliable server-side churn-signal event tracking for any Node.js backend.

Readme

@whisperr/node

The Whisperr server-side SDK — reliable churn-signal event tracking for any Node.js backend. The backend is where the highest-signal churn events live (payment failures, cancellations, trial expiry, usage drops), so this is where Whisperr gets its most valuable signal.

npm install @whisperr/node

Quick start

import { createWhisperr } from "@whisperr/node";

const whisperr = createWhisperr({ apiKey: process.env.WHISPERR_API_KEY! });

// A server-side churn signal:
whisperr.track("user_8842", "payment_failed", { amount_cents: 4900, reason: "card_declined" });

// Associate traits / contact channels with a user:
whisperr.identify("user_8842", { email: "[email protected]", traits: { plan: "pro" } });

// Deliver everything before the process exits:
await whisperr.shutdown();

The user id (externalUserId) is always explicit here — unlike the browser SDK, the server has no persisted session to infer it from. Pass the same id you use everywhere else for that user, and frontend + backend events land on one timeline automatically.

Design

  • Same wire contract as the web SDK. Events post to /v1/events/batch, identities to /v1/identify, authenticated with X-API-Key.
  • Reliable while the process is alive. In-memory queue, batching, retry with backoff (429/5xx), malformed-4xx drop, per-event idempotency key. On 401/403 or exhausted retries, delivery pauses and the batch stays queued for the next flush. The queue is not crash-durable — in serverless or before exit, call await flush() / shutdown() so unsent events aren't lost.
  • Non-blocking. track()/identify() enqueue and return immediately; delivery happens in the background. await flush() when you need a barrier.
  • Process-friendly. The flush timer is unref'd so it never keeps your process alive; call shutdown() for a clean exit.
  • Zero runtime dependencies. Uses the global fetch (Node 18+).

Express

import { createWhisperr } from "@whisperr/node";
import { whisperrExpress } from "@whisperr/node/express";

const whisperr = createWhisperr({ apiKey: process.env.WHISPERR_API_KEY! });

app.use(whisperrExpress(whisperr)); // after your auth middleware

app.post("/billing/webhook", (req, res) => {
  req.whisperr.track("payment_failed", { amount_cents: 4900 });
  res.sendStatus(200);
});

req.whisperr.track() is bound to the request's user (resolved from common auth shapes by default, or via resolveUser). For events with no request — Stripe webhooks, cron jobs — call whisperr.track(userId, …) directly with the id from your domain data.

Serverless

In short-lived environments (Lambda, Vercel functions), await whisperr.flush() before returning so queued events aren't lost when the runtime freezes.

Options

| Option | Default | Notes | |---|---|---| | apiKey | — | App ingestion key (wrk_…). Required. | | baseUrl | https://api.whisperr.net | Ingestion base URL. | | flushAt | 20 | Flush when this many events are queued. | | flushIntervalMs | 10000 | Background flush cadence. 0 disables the timer. | | maxQueueSize | 10000 | Oldest events drop on overflow. | | maxBatchSize | 500 | Events per batch (hard backend cap is 500). | | maxRetries | 6 | Consecutive retries before backing off. | | requestTimeoutMs | 10000 | Per-request timeout. | | disabled | false | No-op client (useful in tests). | | debug | false | Verbose logging. | | onError | — | (error) => void for delivery/drop observability. | | fetch | global fetch | Inject for tests or custom runtimes. |


Whisperr — predict churn, automate interventions, recover revenue. whisperr.net