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

@brooswit/sundry

v0.2.2

Published

A toolbox of small, well-tested TypeScript utilities

Readme

@brooswit/sundry

A toolbox of small, well-tested TypeScript utilities. Each one is independent; add more as you go.

watch(fn, onChange, intervalMs, options?)

Polls fn on an interval and calls onChange(next, prev) whenever the value changes. Returns a stop().

import { watch } from "@brooswit/sundry";

const stop = watch(
  () => fs.statSync("config.json").mtimeMs,   // sync or async
  (next, prev) => console.log("changed", prev, "→", next),
  1000,
);
// ...later
stop();   // idempotent
  • The first call is a baseline — it captures the initial value and does not fire onChange.
  • Change is detected by a stable, order-independent hash, so {a:1,b:2}{b:2,a:1} is not a change.
  • Adaptive cadence. Each tick runs the interval timer and fn at once; the next tick begins when both finish — max(interval, fn-duration). A fast fn keeps a steady interval; a slow fn runs back-to-back with no gap and no dropped ticks. A tick never overlaps the next.
  • fn may be sync or async.
  • A throw/reject skips that tick (no change, baseline unchanged). Pass options.onError to observe it.
  • options: onError?, hash? (override the hash), setTimeout?/clearTimeout? (inject timers, e.g. for tests).

Also exported: hashValue, stableStringify, fnv1a.

Development

bun run check       # generate + typecheck + tests + coverage ≥90%   (what CI runs)
bun test

Every change to src/ needs a CHANGELOG.md entry and a version bump (CI enforces it); merges to main publish to npm with provenance.