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/please

v0.15.1

Published

Nwire — operator CLI. runPlease dispatches actions/queries by name across all registered apps; --tenant for tenant scoping; --help lists everything.

Readme

@nwire/please

Operator CLI — dispatch any registered action or query (and operator-script commands) from the command line.

runPlease({ apps, commands, argv }) boots every registered app, looks up the named target in the supplied commands first (operator scripts take precedence) then in each app's action/query surface, seeds an envelope, dispatches, prints the result. Same handlers as HTTP/queue — operator parity guaranteed.

pnpm add @nwire/please

Quick example

#!/usr/bin/env node
import { runPlease, defineCommand } from "@nwire/please";
import { z } from "zod";
import { apps } from "../app/apps";

const backfillUsers = defineCommand("backfill-users", {
  describe: "Re-hydrate users from the external source",
  args: z.object({ since: z.string().optional() }),
  handler: async ({ args, ctx }) => {
    const repo = ctx.resolve<UserRepo>("UserRepo");
    return { updated: await repo.backfill(args) };
  },
});

const code = await runPlease({
  apps,
  commands: [backfillUsers],
  argv: process.argv.slice(2),
});
process.exit(code);
please backfill-users --since 2026-01-01    # operator script (takes precedence)
please submissions.flag-for-review --submissionId xyz --confidence 0.4
please lessons.start-attempt --lessonId hebrew-1 --studentId avi
please submissions.by-student --studentId avi --status under-review
please --help

Surface

| Export | Role | | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | | runPlease({ apps, commands?, argv, … }) | Boot apps, dispatch one target, return exit code (0 / 1). | | defineCommand(name, meta) | Operator-script primitive. { describe?, args?, handler }. | | CommandDefinition / CommandContext / CommandHandler / CommandMeta / CommandArgsSchema | Types for command authors and consumers. |

Resolution order

runPlease resolves argv[0] in this order:

  1. commands[] — operator scripts shadow domain names on purpose.
  2. Any app's action surface.
  3. Any app's query surface (projection-backed reads).

Args parsers are duck-typed — any object with .parse(input) → output works, so a z.object({...}) schema is the obvious choice.

defineCommand captures $source so Studio's Commands page can render IDE-link chips.

Related

  • @nwire/forge — supplies the App / AppDefinition / HandlerContext types runPlease and defineCommand build on.
  • @nwire/clinwire please <name> delegates to this package.
  • @nwire/scan — emits .nwire/commands.json so Studio + AI surfaces see every operator script.

Status

v0.x — runPlease argv contract + defineCommand shape are locked. Scaffolders (make:module, make:action) land on top in a follow-up.