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

@notifizz/nodejs

v2.2.0

Published

JavaScript/TypeScript client for tracking events with Notifizz. Use it to emit events that drive campaigns server-side and to generate hashed user tokens for the Notification Center widget.

Readme

@notifizz/nodejs

JavaScript/TypeScript client for tracking events with Notifizz. Use it to emit events that drive campaigns server-side and to generate hashed user tokens for the Notification Center widget.

Installation

npm install @notifizz/nodejs
# or
yarn add @notifizz/nodejs

Usage

Initialize the client

const { NotifizzClient } = require("@notifizz/nodejs");
// or ESM: import { NotifizzClient } from "@notifizz/nodejs";

const client = new NotifizzClient(
  "AUTH_SECRET_KEY",  // provided by Notifizz
  "SDK_SECRET_KEY"    // provided by Notifizz
);

Track events

await client.track("user_signed_up", {
  plan: "pro",
  source: "landing_page",
});

// With a caller-supplied idempotency key (recommended for retried jobs):
await client.track("user_signed_up", { plan: "pro" }, { idempotencyKey: "job-42" });

The Notifizz backend resolves campaigns by event name and runs each campaign's orchestrator server-side to build the recipient list — there is no client-side workflow or recipient targeting.

Generate a hashed user token

Use this for backend authentication (e.g. Notification Center).

const token = client.generateHashedToken("user_123");

API summary

| Method | Description | |--------|-------------| | new NotifizzClient(authSecretKey, sdkSecretKey, webhookSigningSecret?) | Create a client. webhookSigningSecret is required only when exposing enrichers via handler(). | | client.track(eventName, properties?, { idempotencyKey? }?) | Track an event. Properties default to {}; idempotency key auto-generated. | | client.generateHashedToken(userId) | Generate a hashed token for the user. | | client.enricher(name, options) | Register an enricher on this client. | | client.handler() | Return a framework-agnostic HTTP handler for enricher discovery + execution. | | client.config({ baseUrl? }) | Configure options (e.g. API base URL). | | client.ready() | Signal that the dispatch endpoint is mounted and serving. Call once the server is listening (app.listen(port, () => client.ready())). Lets a non-production environment re-run discovery so freshly added enrichers / event properties are picked up immediately. No-op effect in production. |