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

@nwire/cli

v0.15.1

Published

Nwire CLI — branded TUI. Dev, run, please, build, test, fmt, lint, check, ps, logs, cache, ls, studio. One surface for the whole framework.

Readme

@nwire/cli

The nwire umbrella CLI — dev, run, cache, studio, please, ls, trace, watch, replay, infra, …

Built on citty: one root command per file under commands/. Long-lived processes (dev, run, studio) go through @nwire/kernel; build/quality passthroughs (fmt, lint, check, test) shell out. Reads nwire.config.ts (or falls back to convention) to locate the consumer's apps registry and the .nwire/ cache.

pnpm add -D @nwire/cli

After install the nwire binary is on node_modules/.bin.

Commands

# Run / develop
nwire dev              # boot every app in the registry, hot-reload
nwire run <wire>       # boot one wire
nwire ps               # list running processes
nwire logs <wire>      # tail logs

# Static + dynamic introspection
nwire cache            # rebuild .nwire/*.json from source
nwire ls               # list actions / events / actors per app
nwire studio           # open Studio against the cache + live runtime

# Live observability (hooks + events)
nwire trace [--correlation <id>] [--limit N]
                       # tail event stream from a running wire; with --correlation
                       # renders the causation tree.
nwire watch <hook> [--limit N]
                       # tail hook-step telemetry. Supports wildcards:
                       # `nwire watch plugin.boot:*`
nwire replay --file <recording.json> [--hook <name>]
                       # replay a recorded hook run against the live wire,
                       # or print an offline trace.

# Operator
nwire please <action> [--<arg> <value> ...]
                       # dispatch an action / query / defineCommand

# Quality + build
nwire fmt / nwire lint / nwire check / nwire test / nwire build

# Misc
nwire infra up         # docker-compose up (postgres/redis/mongo/mailhog/logto/minio)
nwire doctor           # environment + config sanity check

Running nwire with no args prints a greeting + the command list.

Surface

| Export | Role | | ------------------------------- | --------------------------------------------------- | | nwire binary | One subcommand per file under src/commands/. | | loadConfig(cwd) | Programmatic config loader. | | resolveAppsEntry(cwd, config) | Locate the apps registry from convention or config. |

Adding a command: write src/commands/<name>.ts with citty's defineCommand, register it in src/cli.ts. To make it reachable from Studio + MCP, register a kernel router handler too.

Related

  • @nwire/kernel — host for long-lived processes; the CLI delegates dev/run/studio to it.
  • @nwire/scannwire cache writes .nwire/*.json via this package.
  • @nwire/pleasenwire please delegates here.
  • @nwire/mcp — same kernel router exposed to AI clients over stdio.
  • @nwire/studionwire studio boots the Vite dev server for it.

Status

v0.x — command surface is additive. trace / watch / replay operate on the runtime's /__nwire/* HTTP+SSE endpoints; offline modes fall back to .nwire/ cache where possible.