Commander.js


The complete solution for node.js command-line interfaces.

Read this in other languages: English | 简体中文

- Commander.js
- Installation
- Quick Start
- Declaring _program_ variable
- Options
- Common option types, boolean and value
- Default option value
- Other option types, negatable boolean and boolean|value
- Required option
- Variadic option
- Version option
- More configuration
- Custom option processing
- Commands
- Command-arguments
- More configuration
- Custom argument processing
- Action handler
- Stand-alone executable (sub)commands
- Life cycle hooks
- Automated help
- Custom help
- Display help after errors
- Display help from code
- .name
- .usage
- .description and .summary
- .helpOption(flags, description)
- .helpCommand()
- More configuration
- Custom event listeners
- Bits and pieces
- .parse() and .parseAsync()
- Parsing Configuration
- Legacy options as properties
- TypeScript
- createCommand()
- Node options such as --harmony
- Debugging stand-alone executable subcommands
- npm run-script
- Display error
- Override exit and output handling
- Additional documentation
- Support
- Commander for enterprise

For information about terms used in this document see: terminology

Installation

``sh
npm install commander
`

Quick Start

You write code to describe your command line interface.
Commander looks after parsing the arguments into options and command-arguments,
displays usage errors for problems, and implements a help system.

Commander is strict and displays an error for unrecognised options.
The two most used option types are a boolean option, and an option which takes its value from the following argument.

Example file: split.js

`js
const { program } = require('commander');

program
.option('--first')
.option('-s, --separator ');

program.parse();

const options = program.opts();
const limit = options.first ? 1 : undefined;
console.log(program.args[0].split(options.separator, limit));
`

`console
$ node split.js -s / --fits a/b/c
error: unknown option '--fits'
(Did you mean --first?)
$ node split.js -s / --first a/b/c
[ 'a' ]
`

Here is a more complete program using a subcommand and with descriptions for the help. In a multi-command program, you have an action handler for each command (or stand-alone executables for the commands).

Example file: string-util.js

`js
const { Command } = require('commander');
const program = new Command();

program
.name('string-util')
.description('CLI to some JavaScript string utilities')
.version('0.8.0');

program.command('split')
.description('Split a string into substrings and display as an array')
.argument('', 'string to split')
.option('--first', 'display just the first substring')
.option('-s, --separator ', 'separator character', ',')
.action((str, options) => {
const limit = options.first ? 1 : undefined;
console.log(str.split(options.separator, limit));
});

program.parse();
`

`console
$ node string-util.js help split
Usage: string-util split [options]

Split a string into substrings and display as an array.

Arguments:
string string to split

Options:
--first display just the first substring
-s, --separator separator character (default: ",")
-h, --help display help for command

$ node string-util.js split --separator=/ a/b/c
[ 'a', 'b', 'c' ]
`

More samples can be found in the examples directory.

Declaring _program_ variable

Commander exports a global object which is convenient for quick programs.
This is used in the examples in this README for brevity.

`js
// CommonJS (.cjs)
const { program } = require('commander');
`

For larger programs which may use commander in multiple ways, including unit testing, it is better to create a local Command object to use.

`js
// CommonJS (.cjs)
const { Command } = require('commander');
const program = new Command();
`

`js
// ECMAScript (.mjs)
import { Command } from 'commander';
const program = new Command();
`

`ts
// TypeScript (.ts)
import { Command } from 'commander';
const program = new Command();
`

Options

Options are defined with the .option() method, also serving as documentation for the options. Each option can have a short flag (single character) and a long name, separated by a comma or space or vertical bar ('|').

The parsed options can be accessed by calling .opts() on a Command object, and are passed to the action handler.

Multi-word options such as "--template-engine" are camel-cased, becoming program.opts().templateEngine etc.

An option and its option-argument can be separated by a space, or combined into the same argument. The option-argument can follow the short option directly or follow an = for a long option.

`sh
serve -p 80
serve -p80
serve --port 80
serve --port=80
`

You can use -- to indicate the end of the options, and any remaining arguments will be used without being interpreted.

By default, options on the command line are not positional, and can be specified before or after other arguments.

There are additional related routines for when .opts() is not enough:

- .optsWithGlobals() returns merged local and global option values
- .getOptionValue() and .setOptionValue() work with a single option value
- .getOptionValueSource() and .setOptionValueWithSource() include where the option value came from

$3

The two most used option types are a boolean option, and an option which takes its value
from the following argument (declared with angle brackets like --expect ). Both are undefined unless specified on command line.

Example file: options-common.js

`js
program
.option('-d, --debug', 'output extra debugging')
.option('-s, --small', 'small pizza size')
.option('-p, --pizza-type ', 'flavour of pizza');

program.parse(process.argv);

const options = program.opts();
if (options.debug) console.log(options);
console.log('pizza details:');
if (options.small) console.log('- small pizza size');
if (options.pizzaType) console.log(- ${options.pizzaType});
`

`console
$ pizza-options -p
error: option '-p, --pizza-type ' argument missing
$ pizza-options -d -s -p vegetarian
{ debug: true, small: true, pizzaType: 'vegetarian' }
pizza details:
- small pizza size
- vegetarian
$ pizza-options --pizza-type=cheese
pizza details:
- cheese
`

Multiple boolean short options may be combined following the dash, and may be followed by a single short option taking a value.
For example -d -s -p cheese may be written as -ds -p cheese or even -dsp cheese.

Options with an expected option-argument are greedy and will consume the following argument whatever the value.
So --id -xyz reads -xyz as the option-argument.

program.parse(arguments) processes the arguments, leaving any args not consumed by the program options in the program.args array. The parameter is optional and defaults to process.argv.

$3

You can specify a default value for an option.

Example file: options-defaults.js

`js
program
.option('-c, --cheese ', 'add the specified type of cheese', 'blue');

program.parse();

console.log(cheese: ${program.opts().cheese});
`

`console
$ pizza-options
cheese: blue
$ pizza-options --cheese stilton
cheese: stilton
`

$3

You can define a boolean option long name with a leading no- to set the option value to false when used.
Defined alone this also makes the option true by default.

If you define --foo first, adding --no-foo does not change the default value from what it would
otherwise be.

Example file: options-negatable.js

`js
program
.option('--no-sauce', 'Remove sauce')
.option('--cheese ', 'cheese flavour', 'mozzarella')
.option('--no-cheese', 'plain with no cheese')
.parse();

const options = program.opts();
const sauceStr = options.sauce ? 'sauce' : 'no sauce';
const cheeseStr = (options.cheese === false) ? 'no cheese' : ${options.cheese} cheese;
console.log(You ordered a pizza with ${sauceStr} and ${cheeseStr});
`

`console
$ pizza-options
You ordered a pizza with sauce and mozzarella cheese
$ pizza-options --sauce
error: unknown option '--sauce'
$ pizza-options --cheese=blue
You ordered a pizza with sauce and blue cheese
$ pizza-options --no-sauce --no-cheese
You ordered a pizza with no sauce and no cheese
`

You can specify an option which may be used as a boolean option but may optionally take an option-argument
(declared with square brackets like --optional [value]).

Example file: options-boolean-or-value.js

`js
program
.option('-c, --cheese [type]', 'Add cheese with optional type');

program.parse(process.argv);

const options = program.opts();
if (options.cheese === undefined) console.log('no cheese');
else if (options.cheese === true) console.log('add cheese');
else console.log(add cheese type ${options.cheese});
`

`console
$ pizza-options
no cheese
$ pizza-options --cheese
add cheese
$ pizza-options --cheese mozzarella
add cheese type mozzarella
`

Options with an optional option-argument are not greedy and will ignore arguments starting with a dash.
So id behaves as a boolean option for --id -5, but you can use a combined form if needed like --id=-5.

For information about possible ambiguous cases, see options taking varying arguments.

$3

You may specify a required (mandatory) option using .requiredOption(). The option must have a value after parsing, usually specified on the command line, or perhaps from a default value (say from environment). The method is otherwise the same as .option() in format, taking flags and description, and optional default value or custom processing.

Example file: options-required.js

`js
program
.requiredOption('-c, --cheese ', 'pizza must have cheese');

program.parse();
`

`console
$ pizza
error: required option '-c, --cheese ' not specified
`

$3

You may make an option variadic by appending ... to the value placeholder when declaring the option. On the command line you
can then specify multiple option-arguments, and the parsed option value will be an array. The extra arguments
are read until the first argument starting with a dash. The special argument -- stops option processing entirely. If a value
is specified in the same argument as the option then no further values are read.

Example file: options-variadic.js

`js
program
.option('-n, --number ', 'specify numbers')
.option('-l, --letter [letters...]', 'specify letters');

program.parse();

console.log('Options: ', program.opts());
console.log('Remaining arguments: ', program.args);
`

`console
$ collect -n 1 2 3 --letter a b c
Options: { number: [ '1', '2', '3' ], letter: [ 'a', 'b', 'c' ] }
Remaining arguments: []
$ collect --letter=A -n80 operand
Options: { number: [ '80' ], letter: [ 'A' ] }
Remaining arguments: [ 'operand' ]
$ collect --letter -n 1 -n 2 3 -- operand
Options: { number: [ '1', '2', '3' ], letter: true }
Remaining arguments: [ 'operand' ]
`

For information about possible ambiguous cases, see options taking varying arguments.

$3

The optional version method adds handling for displaying the command version. The default option flags are -V and --version, and when present the command prints the version number and exits.

`js
program.version('0.0.1');
`

`console
$ ./examples/pizza -V
0.0.1
`

You may change the flags and description by passing additional parameters to the version method, using
the same syntax for flags as the option method.

`js
program.version('0.0.1', '-v, --vers', 'output the current version');
`

$3

You can add most options using the .option() method, but there are some additional features available
by constructing an Option explicitly for less common cases.

Example files: options-extra.js, options-env.js, options-conflicts.js, options-implies.js

`js
program
.addOption(new Option('-s, --secret').hideHelp())
.addOption(new Option('-t, --timeout ', 'timeout in seconds').default(60, 'one minute'))
.addOption(new Option('-d, --drink ', 'drink size').choices(['small', 'medium', 'large']))
.addOption(new Option('-p, --port ', 'port number').env('PORT'))
.addOption(new Option('--donate [amount]', 'optional donation in dollars').preset('20').argParser(parseFloat))
.addOption(new Option('--disable-server', 'disables the server').conflicts('port'))
.addOption(new Option('--free-drink', 'small drink included free ').implies({ drink: 'small' }));
`

`console
$ extra --help
Usage: help [options]

Options:
-t, --timeout timeout in seconds (default: one minute)
-d, --drink drink cup size (choices: "small", "medium", "large")
-p, --port port number (env: PORT)
--donate [amount] optional donation in dollars (preset: "20")
--disable-server disables the server
--free-drink small drink included free
-h, --help display help for command

$ extra --drink huge
error: option '-d, --drink ' argument 'huge' is invalid. Allowed choices are small, medium, large.

$ PORT=80 extra --donate --free-drink
Options: { timeout: 60, donate: 20, port: '80', freeDrink: true, drink: 'small' }

$ extra --disable-server --port 8000
error: option '--disable-server' cannot be used with option '-p, --port '
`

Specify a required (mandatory) option using the Option method .makeOptionMandatory(). This matches the Command method .requiredOption().

$3

You may specify a function to do custom processing of option-arguments. The callback function receives two parameters,
the user specified option-argument and the previous value for the option. It returns the new value for the option.

This allows you to coerce the option-argument to the desired type, or accumulate values, or do entirely custom processing.

You can optionally specify the default/starting value for the option after the function parameter.

Example file: options-custom-processing.js

`js
function myParseInt(value, dummyPrevious) {
// parseInt takes a string and a radix
const parsedValue = parseInt(value, 10);
if (isNaN(parsedValue)) {
throw new commander.InvalidArgumentError('Not a number.');
}
return parsedValue;
}

function increaseVerbosity(dummyValue, previous) {
return previous + 1;
}

function collect(value, previous) {
return previous.concat([value]);
}

function commaSeparatedList(value, dummyPrevious) {
return value.split(',');
}

program
.option('-f, --float ', 'float argument', parseFloat)
.option('-i, --integer ', 'integer argument', myParseInt)
.option('-v, --verbose', 'verbosity that can be increased', increaseVerbosity, 0)
.option('-c, --collect ', 'repeatable value', collect, [])
.option('-l, --list ', 'comma separated list', commaSeparatedList)
;

program.parse();

const options = program.opts();
if (options.float !== undefined) console.log(float: ${options.float});
if (options.integer !== undefined) console.log(integer: ${options.integer});
if (options.verbose > 0) console.log(verbosity: ${options.verbose});
if (options.collect.length > 0) console.log(options.collect);
if (options.list !== undefined) console.log(options.list);
`

`console
$ custom -f 1e2
float: 100
$ custom --integer 2
integer: 2
$ custom -v -v -v
verbose: 3
$ custom -c a -c b -c c
[ 'a', 'b', 'c' ]
$ custom --list x,y,z
[ 'x', 'y', 'z' ]
`

Commands

You can specify (sub)commands using .command() or .addCommand(). There are two ways these can be implemented: using an action handler attached to the command, or as a stand-alone executable file (described in more detail later). The subcommands may be nested (example).

In the first parameter to .command() you specify the command name. You may append the command-arguments after the command name, or specify them separately using .argument(). The arguments may be or [optional], and the last argument may also be variadic....

You can use .addCommand() to add an already configured subcommand to the program.

For example:

`js
// Command implemented using action handler (description is supplied separately to .command)
// Returns new command for configuring.
program
.command('clone [destination]')
.description('clone a repository into a newly created directory')
.action((source, destination) => {
console.log('clone command called');
});

// Command implemented using stand-alone executable file, indicated by adding description as second parameter to .command.
// Returns this for adding more commands.
program
.command('start ', 'start named service')
.command('stop [service]', 'stop named service, or all if no name supplied');

// Command prepared separately.
// Returns this for adding more commands.
program
.addCommand(build.makeBuildCommand());
`

Configuration options can be passed with the call to .command() and .addCommand(). Specifying hidden: true will
remove the command from the generated help output. Specifying isDefault: true will run the subcommand if no other
subcommand is specified (example).

You can add alternative names for a command with .alias(). (example)

.command() automatically copies the inherited settings from the parent command to the newly created subcommand. This is only done during creation, any later setting changes to the parent are not inherited.

For safety, .addCommand() does not automatically copy the inherited settings from the parent command. There is a helper routine .copyInheritedSettings() for copying the settings when they are wanted.

$3

For subcommands, you can specify the argument syntax in the call to .command() (as shown above). This
is the only method usable for subcommands implemented using a stand-alone executable, but for other subcommands
you can instead use the following method.

To configure a command, you can use .argument() to specify each expected command-argument.
You supply the argument name and an optional description. The argument may be or [optional].
You can specify a default value for an optional command-argument.

Example file: argument.js

`js
program
.version('0.1.0')
.argument('', 'user to login')
.argument('[password]', 'password for user, if required', 'no password given')
.action((username, password) => {
console.log('username:', username);
console.log('password:', password);
});
`

The last argument of a command can be variadic, and only the last argument. To make an argument variadic you
append ... to the argument name. A variadic argument is passed to the action handler as an array. For example:

`js
program
.version('0.1.0')
.command('rmdir')
.argument('')
.action(function (dirs) {
dirs.forEach((dir) => {
console.log('rmdir %s', dir);
});
});
`

There is a convenience method to add multiple arguments at once, but without descriptions:

`js
program
.arguments(' ');
`

#### More configuration

There are some additional features available by constructing an Argument explicitly for less common cases.

Example file: arguments-extra.js

`js
program
.addArgument(new commander.Argument('', 'drink cup size').choices(['small', 'medium', 'large']))
.addArgument(new commander.Argument('[timeout]', 'timeout in seconds').default(60, 'one minute'))
`

#### Custom argument processing

You may specify a function to do custom processing of command-arguments (like for option-arguments).
The callback function receives two parameters, the user specified command-argument and the previous value for the argument.
It returns the new value for the argument.

The processed argument values are passed to the action handler, and saved as .processedArgs.

You can optionally specify the default/starting value for the argument after the function parameter.

Example file: arguments-custom-processing.js

`js
program
.command('add')
.argument('', 'integer argument', myParseInt)
.argument('[second]', 'integer argument', myParseInt, 1000)
.action((first, second) => {
console.log(${first} + ${second} = ${first + second});
})
;
`

$3

The action handler gets passed a parameter for each command-argument you declared, and two additional parameters
which are the parsed options and the command object itself.

Example file: thank.js

`js
program
.argument('')
.option('-t, --title ', 'title to use before name')
.option('-d, --debug', 'display some debugging')
.action((name, options, command) => {
if (options.debug) {
console.error('Called %s with options %o', command.name(), options);
}
const title = options.title ? ${options.title} : '';
console.log(Thank-you ${title}${name});
});
`

If you prefer, you can work with the command directly and skip declaring the parameters for the action handler. The this keyword is set to the running command and can be used from a function expression (but not from an arrow function).

Example file: action-this.js

`js
program
.command('serve')
.argument('