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

ezcli

v1.5.2

Published

Easily create multi-command CLI apps (similar to git)

Downloads

27

Readme

ezcli npm version

Easily create multi-command CLI apps (similar to git).

ezcli was inspired by the excellent commander.js package. Check it out if you need something more full-featured.

Installation

npm i ezcli -S

Usage

package.json

{
  "name": "cli-app",
  "version": "1.0.0",
  "bin": "./app.js"
}

app.js

#!/usr/bin/env node
const cli = require('ezcli')

cli('cli-app')
  .command('subcommand', () => {
    console.log('in subcommand')
  })
  .command('commandWithArg', (arg) => {
    console.log(`commandWithArgs: ${arg}`)
  })
  .command('optionalParams', (required, optional = 'default') => {
    console.log(`optionalParams: ${required} ${optional}`)
  })
  .process()

Resulting app

~ $ cli-app

  v1.0.0

  Usage: cli-app <command>

  Commands:
    subcommand
    commandWithArg <arg>
    optionalParams <required> [optional = 'default']

~ $ cli-app subcommand
in subcommand

~ $ cli-app commandWithArg

  Usage: cli-app commandWithArg <arg>

~ $ cli-app commandWithArg test
commandWithArgs: test

~ $ cli-app optionalParams

  Usage: cli-app optionalParams <required> [optional = 'default']

~ $ cli-app optionalParams abc
optionalParams: abc default

~ $ cli-app optionalParams abc 123
optionalParams: abc 123

API

cli(name:string)

Declare the cli app with the given name. The name should match the defined binary name in your package.json (more info).

command(name:string, fn:function)

Define a subcommand with a given name. Names should be unique and should contain no whitespace. fn will be executed when this subcommand is invoked.

Any parameters defined in fn will become part of the command signature. E.g., command('test', (thing) => {}) will produce the signature test <thing>.

Optional parameters are acceptible, but only at the end of the parameter list. E.g., command('test', (a, b='default') => {}) will produce test <a> [b='default'].

command is chainable, so you may add several commands in sequence.

process()

process is used to indicate the end of your cli app definition. Once it is called, it will beging processing any command line arguments passed in to your cli app, and will execute the correct subcommand or print usage information.

Assumptions and Considerations

ezcli assumes there is a version defined in your package.json. It will automatically use this as part of your app usage message.

ezcli requires node version >= 6.0.0. It is recommended that you set the required minimum node version within your package.json (more info)