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

@clickroom/sdk-node

v0.1.0

Published

Node.js server SDK for Clickroom — product analytics, feature flags and experiments.

Readme

@clickroom/sdk-node

Server-side event capture + local feature-flag evaluation for Node 22+. No autocapture — there's no DOM to observe server-side, so events are explicit capture/identify calls.

import { ClickroomClient } from '@clickroom/sdk-node'

const clickroom = new ClickroomClient({
  writeKey: process.env.CLICKROOM_WRITE_KEY!,
  readKey: process.env.CLICKROOM_READ_KEY, // optional, required for feature flags
  host: 'https://i.clickroom.co',
})

clickroom.capture({
  distinctId: user.id, // required — no client-side persisted identity on the server
  event: 'checkout_completed',
  properties: { plan: 'pro', amount: 49 },
})

clickroom.identify({ distinctId: user.id, properties: { email: user.email, plan: 'pro' } })

if (clickroom.isFeatureEnabled('new-checkout', user.id, { plan: 'pro' })) {
  // ...
}

Flags

Flags are evaluated locally: the client polls GET /v1/flag-definitions (requires readKey) on flagPollInterval (default 30s) and evaluates in-process using the same D-05 SHA1 hash as the browser SDK and the Rust evaluator — guaranteed identical results for the same distinct_id.

Error handling

capture()/identify() events are batched and POSTed to {host}/v1/capture. If the server rejects a batch outright (HTTP 4xx other than 429, e.g. a schema-invalid event under strict validation), the client does not retry — retrying a request the server will never accept would just waste the retry budget. The batch is dropped and the failure is surfaced via console.warn, including the response body (e.g. { accepted, errors }) when the server returns one. Network errors, 429 (rate limiting), and 5xx responses are unaffected — the client retries those with its existing bounded exponential backoff (maxRetries, default 5).

Shutdown

The client buffers events and flushes on size (flushAt, default 20) or interval (flushInterval, default 10s). It registers SIGTERM/SIGINT/beforeExit handlers to flush on process exit. In short-lived scripts (e.g. serverless handlers, CLI tools), call await clickroom.shutdown() explicitly before the process exits to guarantee delivery.