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

supercmd

v2.0.1

Published

SuperCommand is a framework to build command-line interfaces in node.js.

Downloads

53

Readme

SuperCMD

SuperCMD is a framework to build command-line interfaces in Node.js

Usage

// commands/list.js
import { Command } from 'supercmd'

export const command = new Command()

command
  .cmd('list [options]')
  .description('List todos')
  .option('-s, --sort', 'Example of a boolean parameter')
  .option('-n, --num-items [num]', 'Example of an optional numeric parameter')
  .option('--filter [str]', 'Example of an optional string parameter')
  .action((ctx) => {
    // place command's code here
  })
// commands/create.js
import { Command } from 'supercmd'

export const command = new Command()

command
  .cmd('create')
  .description('Create todo')
  .input('Enter a title', 'Example of an optional string parameter')
  .action((ctx) => {
    // place command's code here
  })

Command entrypoint

The entrypoint file loads the command files from a directory.

#!/usr/bin/env node
require('firescript/register')
const {CommandsList} = require('supercmd')

const supercmd = new CommandsList()
supercmd.importFromDir(`${__dirname}/cli`).then((commandList) => {
  if (process.argv[2] === 'help') {
    commandList.printHelpPage(process.argv[3])
    return
  }

  if (process.argv[2] === 'commands') {
    commandList.printCommandsList(process.argv[3])
    return
  }

  commandList.callCommand(process.argv)
}).catch ((err) => {
  console.error(err)
  process.exit(1)
})

API

.cmd(str command)

Register a subcommand. A subcommand can take 0 - n arguments.

Wrap argument types in [ and ]. An leading ? marks it as optional. Command types are either str or num

Example: mycommand [str] [str?] This would register a command mycommand with two arguments. The second one is optional. Both arguments are handled as strings. You can access the arguments as second and third arguments in the action handler.

.action((ctx, infile, outfile) => {

})

.cwd(str workingDir)

Set a working dir

.description(str description)

Describe what a program is for and what is does, show in the help page

.option(str arg, str description, any defaultValue, func func)

Register an option parameter. The param argument describes the parameter name, alias, value und value type. The syntax is [alias] [name] [value].

Alias is an one char long shortcut of the parameter and it is prefixed by one minus char. Example: -f.
Name is a parameter name. It is prefixed by two minus and its the only required part. A parameter can contain chars, numbers and a minus. Example: --fruit, --fruit-banana. The third part describes the parameter value and if it is a mandatory parameter or not. The default type is bool. The type must be enclosed by square bracets. A leading ? in the value type defines the parameter as optional.

Example for a required parameter of type boolean: -f --fruit [bool]

Example for a optional parameter of type string: -b --banana [str?]

Allowed types: str, num, arr, bool, json

.input(str name, str question, str type, any values)

Ask for input parameter. All input parameter are available as ctx.input.<name>

.usage(str description)

Describes program usage, shown in the help page.