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

pulse-metrics

v1.0.0

Published

Node.js SDK for Pulse Metrics instance tracking

Readme

pulse-metrics-sdk

Minimal Node.js SDK for Pulse Metrics instance tracking.

Sends a startup event on initialization and schedules periodic heartbeat pings. The instance ID is automatically generated and persisted to disk so the same ID survives restarts.

Requirements

Node.js 18 or later.

Installation

npm install pulse-metrics

Or copy index.ts directly into your project and compile it alongside your code.

Usage

import { init } from 'pulse-metrics';

init('https://analytics.example.com', 'your-service-token');

Call init once, as early as possible during startup (e.g. at the top of your entry file). That's it.

Options

init('https://analytics.example.com', 'your-service-token', {
  // Use a fixed instance ID instead of auto-generating one
  instanceId: 'my-server-1',

  // Heartbeat every 60 seconds instead of the default 24 hours
  heartbeatInterval: 60_000,

  // Disable heartbeats entirely (only send the startup event)
  // heartbeatInterval: false,

  // Custom path for the persisted instance ID file
  persistPath: '/var/lib/myapp/.analytics-id',
});

Option reference

| Option | Type | Default | Description | |---|---|---|---| | instanceId | string | auto | Override the instance ID. Skips persistence. | | heartbeatInterval | number \| false | 86_400_000 (24 h) | Milliseconds between heartbeats. false disables heartbeats. | | persistPath | string | .pulse-metrics-id (cwd) | File path used to persist the auto-generated instance ID. | | debug | boolean | false | When enabled, errors are logged to the console instead of being silently swallowed. |

Notes

  • Network errors are silently ignored — tracking will never crash your app.
  • The heartbeat timer is unreffed (setInterval(...).unref()) so it won't prevent Node.js from exiting naturally.
  • The raw instanceId is never stored by the server — only a derived HMAC key is persisted.

Building

npm install
npm run build

Output is written to dist/.