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

unicommand

v0.0.4

Published

Shared command framework for TypeScript CLIs and MCP servers

Readme

🎺 Overview

Unicommand is a small TypeScript command framework for packages that expose CLIs and MCP servers from the same command definitions.

❓ Motivation

I keep building local tools that need the same boring pieces: command metadata, CLI help, completions, update commands, dev shims, MCP tools, package metadata, and generated README command docs.

Why? Repeating that per package makes command behavior drift. Unicommand centralizes the contract so apps only define commands.

⭐ Features

  • One defineCommand contract for CLI and MCP metadata.
  • Package-aware CLI runner using package.json bin, version, name, and description.
  • Built-in completion and update commands.
  • Local dev command shims with active dev-bin detection.
  • README command docs generated from command definitions.
  • MCP command server helpers for tools and resources.

🚀 Quick Start

  1. Install the package:

    pnpm add unicommand
  2. Define a command:

    import { createCommandAdapters, defineCommand, z } from 'unicommand';
    
    const metadata = defineCommand({
      name: 'hello',
      description: 'Say hello',
      arguments: [{ synopsis: '<name>', description: 'Name to greet' }],
      outputSchema: z.string(),
    });
    
    export const helloCommand = createCommandAdapters({
      metadata,
      handler: ({ name }: { name: string }) => `Hello, ${name}`,
    });
  3. Create a CLI runner:

    #!/usr/bin/env node
    import { createPackageCommandCliRunner } from 'unicommand';
    
    const cli = createPackageCommandCliRunner({
      importMetaUrl: import.meta.url,
    });
    
    if (cli.isDirectRun()) {
      process.exit(await cli.runCli());
    }

🧰 Usage

import {
  createCommandAdapters,
  createPackageCommandCliRunner,
  defineCommand,
  generateReadmeCommandDocs,
  installPackageDevCommands,
  startPackageCommandMcpServer,
  z,
} from 'unicommand';

Common entry points:

  • defineCommand describes a command once.
  • createCommandAdapters exposes CLI and MCP adapters from one handler.
  • createPackageCommandCliRunner builds a package-aware CLI.
  • startPackageCommandMcpServer starts an MCP server from command exports.
  • installPackageDevCommands installs local dev command shims.
  • generateReadmeCommandDocs updates README command blocks.

Add markers to a README:

<!-- <DYNFIELD:COMMANDS> -->
<!-- </DYNFIELD:COMMANDS> -->

Then generate docs:

import { join } from 'node:path';
import { generateReadmeCommandDocs } from 'unicommand';

await generateReadmeCommandDocs({
  binName: 'my-cli',
  commandsDir: join(process.cwd(), 'src', 'commands'),
});
import { installPackageDevCommands } from 'unicommand';

installPackageDevCommands(import.meta.url, {
  commandNames: ['my-clid'],
});

The generated shim runs src/cli.ts, sets the package program-name env var, and lets update detect dev mode.

🛠 Development

Install dependencies:

pnpm install

Run checks:

pnpm check:fix
pnpm typecheck
pnpm build
pnpm knip

Create a changeset before publishing changes:

pnpm changeset

📜 License

MIT