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

@tkeron/commands

v0.4.7

Published

library for handling command line arguments

Downloads

258

Readme

@tkeron/commands

Zero-dependency CLI command parser and router for Bun/Node.js.

Install

bun add @tkeron/commands

Quick Start

import { getCommands } from "@tkeron/commands";

const cli = getCommands("myapp", "1.0.0")
  .addCommand("build")
  .addAlias("b")
  .addDescription("Build the project")
  .addFlag("verbose", "v", "Enable verbose output")
  .addStringOption("output", "o", "Output directory", { default: "./dist" })
  .addPositionedArgument("source")
  .setCallback(console.log)

  .commands()

  .addCommand("serve")
  .addAlias("s")
  .addDescription("Start dev server")
  .addNumberOption("port", "p", "Port number", { default: 3000 })
  .addFlag("open", "o", "Open browser")
  .setCallback(console.log)

  .commands()

  .addHeaderText("MyApp v1.0.0\n")
  .addFooterText("\nDocs: https://example.com");

cli.start();

Usage:

myapp build src --verbose -o dist
myapp serve -p 8080 --open
myapp help
myapp version

API

getCommands(programName, version)

Creates a new Commands instance.

Commands

| Method | Description | | ---------------------- | ------------------------------------------------- | | .addCommand(name) | Add a command, returns CommandFactory | | .addHeaderText(text) | Set help header text | | .addFooterText(text) | Set help footer text | | .start(argv?) | Parse and execute. Uses process.argv by default |

CommandFactory (chaining)

| Method | Description | | ----------------------------------------------------------- | ----------------------------------------- | | .addAlias(alias) | Add command alias | | .addDescription(text) | Set command description | | .addFlag(name, shortFlag?, description?) | Add boolean flag (--verbose, -v) | | .addStringOption(name, shortFlag?, description?, config?) | Add string option | | .addNumberOption(name, shortFlag?, description?, config?) | Add number option | | .addOption(name, example?) | Add legacy key=value option | | .addPositionedArgument(name) | Add positional argument | | .setCallback(fn) | Set command handler | | .commands() | Return to Commands to add more commands |

Option Config

addStringOption and addNumberOption accept an optional config object:

{
  default?: string | number | boolean;
  required?: boolean;
  aliases?: string[];
  allowedValues?: (string | number)[];
  valueName?: string;
}

Syntax Support

Both syntaxes work and can be mixed:

Standard (new):

myapp build --verbose --output dist
myapp build -v -o dist
myapp build -vw              # combined short flags
myapp build --no-verbose     # negated flags
myapp build -- --not-parsed  # stop parsing after --

Legacy (backward compatible):

myapp build output=dist format=json

Built-in Commands

help and version are added automatically.

License

MIT