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 🙏

© 2024 – Pkg Stats / Ryan Hefner

sb-command

v2.0.6

Published

CLI command and options parser

Downloads

21

Readme

sb-command

sb-command is the CLI parser you'll ever need.

Documentation

There are several types of parameters

  • [name] means name is an optional parameter
  • <name> means name is a required parameter
  • [name...] means name is an optional variadic parameter
  • <name...> means name is a required variadic parameter
  • Specifying no parameter with an option means it's boolean

To add nested commands, simply join them with dot. For example for remote add use remote.add as the command name.

To add configs specific to certain commands, do the .option() call after that particular .command() call. If you want your configs to be global, add them before adding any other command.

Example

const command = require('sb-command')

command
  .version('0.0.1')
  .description('Git Versonal Control System')
  .option('--disable-cache', 'Disable Git Cache')
  .command('init', 'Initialize an empty repo', function(options) {
    console.log('git-init')
  })
  .option('--shallow-copy', 'Initialize with shallow copy')
  .command('add [file]', 'Add file contents to index', function(options, file) {
    console.log('git-add', files)
  })
  .option('--dry-run', 'Try to stage the file into git index but dont actually do it')
  .default(function(options, parameters) {
    console.log(options, parameters)
  })
  .process()

API

export class Command {
  default(callback: Function): this
  version(version: string): this
  description(descriptionText: string): this
  command(commandName: string, description: string, callback: ?Function): this
  option(option: string, description: string, defaultValue: any = null): this
  process(argv: Array<string> = process.argv): Promise<any>
  showHelp(): string
}
export default new command

LICENSE

This package is licensed under the terms of MIT License. See the LICENSE file for more info.