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

@nyatinte/prw

v0.4.1

Published

Interactive pnpm workspace package & script runner

Readme

@nyatinte/prw

English | 日本語

CI npm downloads pnpm

prw is a CLI for interactively selecting a package and script in a pnpm workspace and running it. It only uses existing package.json scripts — no extra config files required.

Demonstration of the prw CLI's interactive workflow

Installation

npm install -g @nyatinte/prw
# or
pnpm add -g @nyatinte/prw

Usage

1. Start without arguments

prw

Interactively select a package and script, then run it. The root package is also available.

2. Pass a package name

prw web

Package names are matched with fuzzy search. If one package matches, it goes straight to script selection. If multiple match, the package picker is shown. Frequently used packages are shown first based on history.

3. Pass both package and script

prw @myapp/web dev

If both are unambiguous, prw skips the selection screens and runs immediately. Frequently used scripts are also shown first based on history.

[!NOTE] You don't need to type the full package name every time. A short query like prw web is usually enough.

Example

$ prw
│
◆  Select package
│
│  Search: _
│  ● (root)
│  ○ @myapp/web
│  ○ @myapp/api
│  ↑/↓ to select • Enter: confirm • Type: to search
└

After selecting a package, you move on to script selection. The focused script shows its full command in (...).

│
◇  Select package
│  @myapp/web
│
◆  Select script
│
│  Search: _
│  ● dev (vite)
│  ○ build
│  ○ test
│  ↑/↓ to select • Enter: confirm • Type: to search
└

Workspace Layout

.
├─ package.json
├─ pnpm-workspace.yaml
├─ apps/
│  └─ web/
│     └─ package.json
└─ packages/
   ├─ ui/
   │  └─ package.json
   └─ config/
      └─ package.json

With a monorepo like this, you can run scripts from anywhere under apps/ or packages/, from anywhere in the workspace.

Spec

[!IMPORTANT] prw can be run from anywhere inside the workspace. It walks up parent directories to find the nearest pnpm-workspace.yaml.

[!NOTE] Usage history is stored per workspace at $XDG_STATE_HOME/prw/histories/<workspace-id>.json (or ~/.local/state/prw/histories/<workspace-id>.json when XDG_STATE_HOME is unset). <workspace-id> is a SHA-256 hash of the resolved workspace root path.

License

MIT