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

shocking

v1.0.2

Published

Overlay Mount HTTP Development Server

Readme

shocking

Zero-dependency static file server with union-mount layering.

Usage

shocking [options] <base-dir> [overlay-dir...]

| Option | Default | Description | |--------|---------|-------------| | -p, --port <n> | 8080 | Port to listen on | | -o, --open | — | Open browser on start | | -s, --https | — | HTTPS (coming soon) |

How it works

The first argument is the HTTP root (/). Every additional directory is mounted at /<dirname> on top of it. Files in an overlay shadow files in the base at that path; everything else falls through to the base. This is union-mount semantics — no files are hidden unless explicitly overridden.

shocking base-app project-2
/                 → base-app/
/project-2/       → project-2/   (shadows base-app/project-2/ if it exists)

Inspectoid example

shocking ~/inspectoid/  ~/themes/workflow/.inspectoid

Requests to /.inspectoid/* are served from the theme's .inspectoid directory first, then fall back to the SPA's own .inspectoid. Everything else (/index.html, /app.js, …) comes from the base.

/_mounts

Every server exposes a /_mounts endpoint so SPAs can discover what's layered at runtime:

{
  "base": "/path/to/base-app",
  "overlays": [
    { "mountPath": "/project-2", "diskPath": "/path/to/project-2" }
  ]
}

Demo

node cli.js -p 3000 example/base-app example/project-2

Open http://localhost:3000 to see the union-mount in action.