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

runshot

v0.1.20

Published

See your whole product from one config — every screen, every email, and a flow diagram. A QA artifact and deterministic CI gate for builders who ship fast.

Readme

runshot

One-shot a complete visual record of any web app — every screen, email, and social/link preview, plus a video — laid out as a browsable flow canvas (Figma export optional).

Quick start (npx)

npx runshot setup                                       # one-time: install Chromium
npx runshot record --config ./runshot/skills.config.json
npx runshot serve                                       # browse captured runs at :8080

runshot assert is the same capture but exits non-zero on failure — use it as a CI gate. Config defaults to ./runshot/skills.config.json.

Hosting & base path

runshot serve runs a hub at :8080 that lists every project under ~/github/*/runshot/artifacts and serves each one under its folder name. It can be mounted at the root or under a sub-path via environment variables (see .env.example):

| Var | Default | Purpose | | --- | --- | --- | | PORT | 8080 | Port to bind. Fails loudly if busy — never auto-increments. | | HOST | 0.0.0.0 | Interface to bind (127.0.0.1 when behind a reverse proxy). | | BASE_PATH | / | URL prefix. / = root; /runshot = mount everything under /runshot. | | PUBLIC_BASE_URL | http://localhost:8080 | Canonical external URL, including the base path. |

All internal links, redirects, asset paths, and API calls respect BASE_PATH, so clicking an app card stays under the prefix (e.g. /runshot/heirlooming/ instead of escaping to /heirlooming/). A health endpoint is served at <base>/api/health.

Examples

# Local dev (root)
PORT=8080 HOST=0.0.0.0 BASE_PATH=/ PUBLIC_BASE_URL=http://localhost:8080 \
  npx runshot serve

# Local network — same as dev; HOST=0.0.0.0 already exposes it on the LAN
#   http://your-machine.local:8080  /  http://192.168.x.x:8080

# Tailscale path mode (https://your-machine.your-tailnet.ts.net/runshot)
PORT=8080 HOST=0.0.0.0 BASE_PATH=/runshot \
  PUBLIC_BASE_URL=https://your-machine.your-tailnet.ts.net/runshot \
  npx runshot serve

# Caddy subdomain mode (https://runshot.example.com) — bind localhost, root path
PORT=8080 HOST=127.0.0.1 BASE_PATH=/ PUBLIC_BASE_URL=https://runshot.example.com \
  npx runshot serve

On startup runshot logs the local URL, the public URL, and the active base path.

Smoke test the base-path behavior with npm test (or node test/smoke.mjs).

Also available as a Claude Code plugin (skills runshot:walkthrough and runshot:flow-doc). Full docs, config reference, and source: https://github.com/arieldiaz/runshot

License

MIT.