To help you get started, we've collected the most common ways that command-line-usage is being used within popular public projects.

open-wc / open-wc / packages / es-dev-server / src / command-line-args.js View on Github

// convert kebab-case to camelCase
  /** @type {object} */
  const args = Object.keys(dashesArgs).reduce((acc, key) => {
    acc[camelcase(key)] = dashesArgs[key];
    return acc;
  }, {});

  if (args.debug) {
    setDebug(true);
  }

  if ('help' in args) {
    /* eslint-disable-next-line no-console */
    console.log(
      commandLineUsage([
        {
          header: 'es-dev-server',
          content: `
          A dev server for modern web development workflows.

          Usage: \`es-dev-server [options...]\`
        `.trim(),
        },
        {
          header: 'Global Options',
          optionList: commandLineOptions,
        },
      ]),
    );
    process.exit();
  }

View more ways to use command-line-usage

command-line-usage

Upgraders, please check the release notes.

A simple, data-driven module for creating a usage guide.

Synopsis

A usage guide is created by first defining an arbitrary number of sections, e.g. a description section, synopsis, option list, examples, footer etc. Each section has an optional header, some content and must be of type content or optionList. This section data is passed to commandLineUsage() which returns a usage guide.

Inline ansi formatting can be used anywhere within section content using chalk template literal syntax.

For example, this script:

import commandLineUsage from 'command-line-usage'

const sections = [
  {
    header: 'A typical app',
    content: 'Generates something {italic very} important.'
  },
  {
    header: 'Options',
    optionList: [
      {
        name: 'input',
        typeLabel: '{underline file}',
        description: 'The input to process.'
      },
      {
        name: 'help',
        description: 'Print this usage guide.'
      }
    ]
  }
]
const usage = commandLineUsage(sections)
console.log(usage)

Outputs this guide:

Some examples

Typical

A fairly typical usage guide with three sections - description, option list and footer. Code.

Option List groups

Demonstrates breaking the option list up into groups. Code.

Banners

A banner is created by adding the raw: true property to your content. This flag disables any formatting on the content, displaying it raw as supplied.

Header

Demonstrates a banner at the top. This example also adds a synopsis section. Code.

Footer

Demonstrates a footer banner. Code.

Examples section (table layout)

An examples section is added. To achieve this table layout, supply the content as an array of objects. The property names of each object are not important, so long as they are consistent throughout the array. Code.

Advanced optionList layout

The optionList layout is fully configurable by setting the tableOptions property with an options object suitable for passing into table-layout. This example overrides the default column widths and adds flame padding. Code.

Command list

Useful if your app is command-driven, like git or npm. Code.

Description section (table layout)

Demonstrates supplying specific table layout options to achieve more advanced layout. In this case the second column (containing the hammer and sickle) has a fixed width of 40 and noWrap enabled (as the input is already formatted as desired). Code.

Real-life

The polymer-cli usage guide is a good real-life example.

Documentation

• API Reference
• The full list of examples

© 2015-24 Lloyd Brookes <75pound@gmail.com>. Documented by jsdoc-to-markdown.