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-to-markdown

v1.2.0

Published

Render the options of a commander app as markdown

Downloads

31

Readme

Coveralls – test coverage
Travis – build status
David – status of dependencies
Code style: airbnb

 

commander-to-markdown

Render the options of a commander app as markdown

 

Installation

$ npm install commander-to-markdown

 

Usage

Say you have a commander app which looks like this:

const program = require('commander');

program
  .arguments('<address>', 'Address for delivery')
  .option('-p, --peppers', 'Add peppers')
  .option('-P, --pineapple', 'Add pineapple')
  .option('-b, --bbq-sauce', 'Add bbq sauce')
  .option('-c, --cheese [type]', 'Pick the type of cheese', 'marble')
  .parse(process.argv);

commanderToMarkdown is pretty much like the require function – only instead of the app itself, you get the program’s options rendered as markdown:

▸ const commanderToMarkdown = require('commander-to-markdown');

▸ commanderToMarkdown(`${__dirname}/app`);
◂ '''
#### `<address>`
Address for delivery.

#### `-p, --peppers`
Add peppers.

#### `-P, --pineapple`
Add pineapple.

#### `-b, --bbq-sauce`
Add bbq sauce.

#### `-c, --cheese [type]`
Pick the type of cheese. Default: `marble`.
'''

 

Demo

Here’s how it looks rendered.

<address>

Address for delivery.

-p, --peppers

Add peppers.

-P, --pineapple

Add pineapple.

-b, --bbq-sauce

Add bbq sauce.

-c, --cheese [type]

Pick the type of cheese. Default: marble.

This looks especially good when rendered as a manpage with marked-man.

 

Preventing the program from executing

To prevent executing the program, we stub out your require('.') and require('..') with an empty function which returns an object. If that’s not enough for you, you can pass us the option programModules:

commanderToMarkdown(`${__dirname/app}`, { programModules: ['.', './logic'] });

 

Caveats

  • At the moment we only accept an absolute path.

 

License

MIT © Studio B12