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

w7s-local

v0.1.10

Published

workerd-powered local W7S routing simulator for app development.

Readme

w7s-local

Local W7S routing simulator for app development, powered directly by workerd.

w7s-local does not require wrangler, a Cloudflare account, KV, R2, or Workers for Platforms. It generates a temporary workerd config, runs a local Worker that mirrors the W7S URL shape, serves static build output from disk, and proxies to a local backend/dev server.

Usage

npx w7s-local --backend http://localhost:5173
npx w7s-local --frontend dist
npx w7s-local --command "npm run dev -- --host 127.0.0.1 --port 5173" --backend http://localhost:5173

Local W7S URL shape:

http://<owner>.local.w7s.cloud:8787/<repo>/
http://<branch>--<owner>.local.w7s.cloud:8787/<repo>/

When DNS for local.w7s.cloud is not available locally, use the host header:

curl -H "host: acme.local.w7s.cloud" http://127.0.0.1:8787/app/

Options

--root <dir>             App root. Defaults to cwd.
--owner <slug>           GitHub owner/org slug. Inferred from git remote when possible.
--repo <slug>            GitHub repo slug. Inferred from package.json or cwd.
--environment <name>     W7S environment. Defaults to production.
--base-domain <domain>   Local W7S base domain. Defaults to local.w7s.cloud.
--port <port>            Local workerd HTTP port. Defaults to 8787.
--frontend <dir>         Static output directory. Auto-detected by W7S conventions.
--backend <url>          Backend/dev server origin to proxy after stripping the repo prefix.
--command <command>      Start a dev command before serving.
--workerd <path>         workerd executable. Defaults to the bundled npm dependency.

What It Simulates

  • W7S host parsing for owner, branch environments, and owner-root apps.
  • Repo prefix stripping before backend proxying.
  • x-w7s-org-slug, x-w7s-repo-slug, and x-w7s-original-path headers.
  • Static output detection for frontend/dist, dist/client, dist, build, and out.
  • Static exact match before backend proxy.
  • SPA fallback after backend 404 or 405.

It intentionally does not emulate KV, R2, D1, Durable Objects, queues, workflows, Workers AI, or Workers for Platforms. Apps should use local service doubles for those bindings during development.

Publishing

The package is published by .github/workflows/publish-w7s-local.yml on every push to main. The workflow uses npm trusted publishing, so it does not need an npm automation token. It queries the latest published version and publishes the next patch version.

Configure npm trusted publishing for:

Package: w7s-local
Provider: GitHub Actions
Organization or user: w7s-io
Repository: w7s-core
Workflow filename: publish-w7s-local.yml
Environment name: leave empty
Allowed actions: npm publish

npm requires the package to exist before a trusted publisher can be configured. For the first registry bootstrap, publish [email protected] once with an npm account that owns the package, then add the trusted publisher above.