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

@silvery/commander

v0.8.1

Published

Colorized Commander.js help output using ANSI escape codes

Readme

@silvery/commander

Type-safe Commander.js with validated options, colorized help, and Standard Schema support. Drop-in replacement — Command extends Commander's Command. Install once, Commander is included.

npm install @silvery/commander

Example

import { Command, z } from "@silvery/commander"

const program = new Command("deploy")
  .description("Deploy services to an environment")
  .version("1.0.0")
  .option("-e, --env <env>", "Target environment", z.enum(["dev", "staging", "prod"]))
  .option("-f, --force", "Skip confirmation")
  .option("-v, --verbose", "Verbose output")

program
  .command("start <service>")
  .description("Start a service")
  .option("-p, --port <n>", "Port number", z.port)
  .option("-r, --retries <n>", "Retry count", z.int)
  .action((service, opts) => {
    /* ... */
  })

program
  .command("stop <service>")
  .description("Stop a running service")
  .action((service) => {
    /* ... */
  })

program
  .command("status")
  .description("Show service status")
  .option("--json", "Output as JSON")
  .action((opts) => {
    /* ... */
  })

program.parse()
const { env, force, verbose } = program.opts()
//      │     │       └─ boolean | undefined
//      │     └────────── boolean | undefined
//      └──────────────── "dev" | "staging" | "prod"

With plain Commander, opts() returns Record<string, any> — every value is untyped. With @silvery/commander, each option's type is inferred from its schema: z.port produces number, z.enum(...) produces a union, z.csv produces string[]. Invalid values are rejected at parse time with clear error messages — not silently passed through as strings.

Zod is entirely optional — z is tree-shaken from your bundle if you don't import it. Without Zod, use the built-in types (port, int, csv) or plain Commander.

Help is auto-colorized — bold headings, green flags, cyan commands, dim descriptions:

Options with Zod schemas or built-in types are validated at parse time with clear error messages.

What's included

  • Colorized help — automatic, with color level detection and NO_COLOR/FORCE_COLOR support via @silvery/ansi (optional)
  • Typed .option() parsing — pass a type as the third argument:
    • 14 built-in types — port, int, csv, url, email, date, more
    • Array choices — ["dev", "staging", "prod"]
    • Zod schemas — z.port, z.int, z.csv, or any custom z.string(), z.number(), etc.
    • Any Standard Schema library — Valibot, ArkType
    • All types usable standalone via .parse()/.safeParse()

Docs

Full reference, type table, and API details at silvery.dev/reference/commander.

Credits

License

MIT