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

live-visitors

v1.0.0

Published

Count page views, unique browsers, and who is on the page right now.

Readme

Live Visitors

Four numbers. They are not the same number.

| Field | What it actually is | | --- | --- | | views | How many times this path was loaded. A refresh counts again. A second tab counts again. | | visitors | Unique browser ids seen by this store. A new browser, or cleared site data, is a new visitor. Not a person. | | today | Those ids that loaded the page on the current UTC day. | | live | Ids with a tab that heartbeated inside the live window (default 20 seconds). Two tabs, one id: 1. |

The browser keeps an id in localStorage (live-visitors-id) and a tab id in sessionStorage (live-visitors-tab). It posts view once per path per document load, then beat every 10 seconds. A refresh counts as another view. React strict mode does not double-count: the view is recorded once per document.

stop() clears the heartbeat. It does not send leave. A tab that navigates away drops out of live when the window passes (default 20 seconds). Closing the tab sends leave on pagehide and drops out immediately.

Install

npm install live-visitors
import { LiveVisitors } from "live-visitors";

const visitors = new LiveVisitors({
  url: "/api/live-visitors",
  onUpdate(snapshot) {
    document.querySelector("#live").textContent = String(snapshot.live);
  },
});
visitors.start();

Server

The package does not phone home. You host the counter. examples/server.mjs is a single-process server:

npm run build
node examples/server.mjs
# POST http://127.0.0.1:8787/  and  GET http://127.0.0.1:8787/?page=/

MemoryCounter is accurate on one long-lived process. A serverless deploy with many isolates will each keep their own map, and the numbers will be wrong. Implement CounterStore (apply, snapshot) on Redis or Postgres if you run more than one process. The memory store resets when the process exits.

POST JSON: { "type": "view" | "beat" | "leave", "visitorId", "tabId", "page" }. Ids are 8–80 characters of [A-Za-z0-9_-]. page is a path starting with /, max 200 characters. GET ?page=/docs returns the snapshot. Responses are cache-control: no-store.