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

slowwatch

v0.1.0

Published

Only log something when it becomes slow — plus automatic regression detection against your own baseline.

Readme

slowwatch

Only log something when it becomes slow.

One small problem. One obvious API. Very little setup. Immediate value.

console.time gives you raw numbers. Raw numbers don't tell you whether performance is getting worse. slowwatch watches every labelled execution, stays silent while things are fast, warns past a budget, and flags regressions against your own baseline.

Install

npm i slowwatch

Usage

import { slow } from "slowwatch";

const user = await slow("load-user", () => getUser());
// fast → prints nothing
// slow → 🐌 "load-user" took 842ms  (Expected < 200ms)

Thresholds

slow("load-user", getUser, { warn: 200, error: 1000 });
// 🐌  warning past 200ms
// 🚨  critical past 1s ("Critical threshold is 1s")

Automatic regression detection

After a few baseline runs, a clearly slower execution is flagged:

Performance regression

"load-user"

Previous average:  112ms
Current:          391ms

249% slower

Manual timer

import { start } from "slowwatch";

const timer = start("database-query");
await query();
timer.end(); // records + warns if slow

Decorator

import { monitorSlow } from "slowwatch";

const loadUser = monitorSlow("load-user", originalLoadUser, { warn: 200 });

Stats

import { stats } from "slowwatch";

stats("load-user");
// { count, avg, median, p95, min, max, latest }

Configure

import { configure, slow } from "slowwatch";

configure({
  output: "console",      // or "silent" | "buffer" | your own logger
  defaults: { warn: 500, error: 5000, baseline: true },
});

Zero dependencies. ESM + CJS + .d.ts. Node >= 18.

License

MIT