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

commander-auto-complete

v0.1.0

Published

Generates a bash compeletion function based on node-commander program instance

Downloads

5

Readme

Commander-Completion

This module can be used to generate bash/zsh completion functions for a commander.js cli.

Requirements

  • your cli is built with node-commander
  • coffeescript is installed on your system
  • your cli can be called with ./cli.coffee example-command

Installation

Installation is 3 step process

  1. npm install commander-completion
  2. copy/source the completion.sh file into your ~/.bashrc or ~/.zshrc
  3. add the following 'completion' script to your package.json
// Your scripts definition inside your package.json might look like this:
"scripts": {
  "test": "echo \"Error: no test specified\" && exit 1",
  "completion": "coffee node_modules/commander-completion/index.coffee >/dev/null"
},
  1. run npm run-script completion to generate the completion options

Updating your completion options

Calling npm run-script completion generates a commands.sh file which is used by the completion function to get the options for the current cli.coffee file. (This allows the completion function (completion.sh) to work across several cli.coffee instances by storing the commands and options in a module-specific location)

This means that whenever you update your CLI with new commands or options, you should re-run npm run-script completion.

If you want this done automatically for you, you could add that script to npm lifecycle hooks, git-hooks, or even run the coffee node_modules/commander-completion/index.coffee directly from your ~/.bashrc or ~/.zshrc