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

cliffy-flat-help

v1.2.2

Published

A flat help text generator for Cliffy - shows all subcommands, arguments, and options in one view

Readme

Cliffy Flat Help

Note: This project is unofficial and unaffiliated with Cliffy. It is a community project created independently.

A configuration for Cliffy which generates the help text (ex. --help) with information about all subcommands, their arguments, their subcommands, etc. in one big help text block at the root.

This is particularly useful for AI agents and automated tools that can run --help once and instantly get complete context on how to use the entire CLI. Note: This is NOT recommended for large CLIs with many subcommands, as the help text can become overwhelmingly large.

Installation

npm install cliffy-flat-help

Usage

Use the flatHelp() helper function in the help() function of your top-level command.

Configuration

The flatHelp() function accepts an optional configuration object:

interface FlatHelpConfig {
  /**
   * Whether to use colors in the help output.
   * Defaults to true.
   */
  colors?: boolean;
}

Example

A runnable example (npm run example -- --help) is available at examples/todo-cli.ts.

import { Command } from "@cliffy/command";
import { flatHelp } from "cliffy-flat-help";

const cli = new Command()
  .name("my-cli")
  .description("My awesome CLI tool")
  .version("1.0.0")
  .help(flatHelp())
  .command("init", new Command()
    .description("Initialize a new project")
    .arguments("<project-name>")
    .option("-t, --template <template>", "Project template to use")
  )
  .command("build", new Command()
    .description("Build the project")
    .option("-w, --watch", "Watch for changes")
    .option("-o, --output <dir>", "Output directory")
  )
  .command("deploy", new Command()
    .description("Deploy to production")
    .arguments("[environment]")
    .option("-f, --force", "Force deployment")
  );

await cli.parse();

When you run my-cli --help, you'll see:

Usage: my-cli [options] [command]

My awesome CLI tool

Commands:
  init <project-name> Initialize a new project
    <project-name>    (Required)                 
    -t, --template   Project template to use    
                                                    
  build               Build the project          
    -w, --watch      Watch for changes          
    -o, --output     Output directory           
                                                    
  deploy [environment] Deploy to production      
    [environment]    (Optional)                 
    -f, --force      Force deployment