pax_global_header00006660000000000000000000000064141750405040014512gustar00rootroot0000000000000052 comment=02a124c7d58dbae2ef11f9284b2c68ad94f6dc8b commander.js-9.0.0/000077500000000000000000000000001417504050400141005ustar00rootroot00000000000000commander.js-9.0.0/.editorconfig000066400000000000000000000003441417504050400165560ustar00rootroot00000000000000# EditorConfig is awesome: http://EditorConfig.org # top-most EditorConfig file root = true [*] end_of_line = lf insert_final_newline = true indent_style = space indent_size = 2 tab_width = 2 # trim_trailing_whitespace = true commander.js-9.0.0/.eslintrc.js000066400000000000000000000026371417504050400163470ustar00rootroot00000000000000const javascriptSettings = { files: ['*.js', '*.mjs'], extends: [ 'standard', 'plugin:jest/recommended' ], rules: { 'no-else-return': ['error', { allowElseIf: false }], 'space-before-function-paren': ['error', 'never'], // manual "semistandard" settings semi: ['error', 'always'], 'no-extra-semi': 'error' } }; const typescriptSettings = { files: ['*.ts'], parserOptions: { project: './tsconfig.json' }, plugins: [ '@typescript-eslint' ], extends: [ 'standard-with-typescript' ], rules: { 'no-else-return': ['error', { allowElseIf: false }], 'space-before-function-paren': 'off', '@typescript-eslint/space-before-function-paren': ['error', 'never'], '@typescript-eslint/member-delimiter-style': [ 'error', { multiline: { delimiter: 'semi', requireLast: true }, singleline: { delimiter: 'semi', requireLast: false } } ], // manual "semistandard" settings semi: 'off', '@typescript-eslint/semi': ['error', 'always'], 'no-extra-semi': 'off', '@typescript-eslint/no-extra-semi': ['error'] } }; module.exports = { plugins: ['jest'], parserOptions: { ecmaVersion: 8 }, overrides: [ javascriptSettings, typescriptSettings, { files: ['*.mjs'], parserOptions: { sourceType: 'module' } } ] }; commander.js-9.0.0/.github/000077500000000000000000000000001417504050400154405ustar00rootroot00000000000000commander.js-9.0.0/.github/FUNDING.yml000066400000000000000000000000731417504050400172550ustar00rootroot00000000000000github: [tj, shadowspawn, abetomo] tidelift: npm/commander commander.js-9.0.0/.github/PULL_REQUEST_TEMPLATE.md000066400000000000000000000025451417504050400212470ustar00rootroot00000000000000# Pull Request ## Problem ## Solution ## ChangeLog commander.js-9.0.0/.github/workflows/000077500000000000000000000000001417504050400174755ustar00rootroot00000000000000commander.js-9.0.0/.github/workflows/tests.yml000066400000000000000000000013341417504050400213630ustar00rootroot00000000000000name: build on: [push, pull_request] jobs: test: name: Test on node ${{ matrix.node-version }} and ${{ matrix.os }} runs-on: ${{ matrix.os }} strategy: fail-fast: false matrix: node-version: [12.x, 14.x, 16.x, 17.x] os: [ubuntu-latest, windows-latest, macos-latest] steps: - uses: actions/checkout@v2 - name: Use Node.js ${{ matrix.node-version }} uses: actions/setup-node@v2 with: cache: 'npm' node-version: ${{ matrix.node-version }} # Use separate run commands so command status handled correctly on Windows - name: npm install run: npm ci - name: npm test run: npm test - name: npm run lint run: npm run lint commander.js-9.0.0/.gitignore000066400000000000000000000000671417504050400160730ustar00rootroot00000000000000.DS_Store node_modules *.sock .idea .vscode/ coverage/ commander.js-9.0.0/CHANGELOG.md000066400000000000000000001244341417504050400157210ustar00rootroot00000000000000# Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). ## [9.0.0] (2022-01-28) ### Added - simpler ECMAScript import ([#1589]) - Option.preset() allows specifying value/arg for option when used without option-argument (especially optional, but also boolean option) ([#1652]) - `.executableDir()` for custom search for subcommands ([#1571]) - throw with helpful message if pass `Option` to `.option()` or `.requiredOption()` ([#1655]) - .`error()` for generating errors from client code just like Commander generated errors, with support for `.configureOutput()`, `.exitOverride()`, and `.showHelpAfterError()` ([#1675]) - `.optsWithGlobals()` to return merged local and global options ([#1671]) ### Changed - *Breaking:* Commander 9 requires Node.js v12.20.0 or higher - update package-lock.json to lockfile@2 format ([#1659]) - `showSuggestionAfterError` is now on by default ([#1657]) - *Breaking:* default value specified for boolean option now always used as default value (see .preset() to match some previous behaviours) ([#1652]) - default value for boolean option only shown in help if true/false ([#1652]) - use command name as prefix for subcommand stand-alone executable name (with fallback to script name for backwards compatibility) ([#1571]) - allow absolute path with `executableFile` ([#1571]) - removed restriction that nested subcommands must specify `executableFile` ([#1571]) - TypeScript: allow passing readonly string array to `.choices()` [(#1667)] - TypeScript: allow passing readonly string array to `.parse()`, `.parseAsync()`, `.aliases()` [(#1669)] ### Fixed - option with optional argument not supplied on command line now works when option already has a value, whether from default value or from previous arguments ([#1652]) ### Removed - *Breaking:* removed internal fallback to `require.main.filename` when script not known from arguments passed to `.parse()` (can supply details using `.name()`, and `.executableDir()` or `executableFile`) ([#1571]) ## [9.0.0-1] (2022-01-15) (Released in 9.0.0) ## [9.0.0-0] (2021-12-22) (Released in 9.0.0) ## [8.3.0] (2021-10-22) ### Added - `.getOptionValueSource()` and `.setOptionValueWithSource()`, where expected values for source are one of 'default', 'env', 'config', 'cli' ([#1613]) ### Deprecated - `.command('*')`, use default command instead ([#1612]) - `on('command:*')`, use `.showSuggestionAfterError()` instead ([#1612]) ## [8.2.0] (2021-09-10) ### Added - `.showSuggestionAfterError()` to show suggestions after unknown command or unknown option ([#1590]) - add `Option` support for values from environment variables using `.env()` ([#1587]) ### Changed - show error for unknown global option before subcommand (rather than just help) ([#1590]) ### Removed - TypeScript declaration of unimplemented `Option` method `argumentRejected` ## [8.1.0] (2021-07-27) ### Added - `.copyInheritedSettings()` ([#1557]) - update Chinese translations of documentation for Commander v8 ([#1570]) - `Argument` methods for `.argRequired()` and `.argOptional()` ([#1567]) ## [8.0.0] (2021-06-25) ### Added - `.argument(name, description)` for adding command-arguments ([#1490]) - supports default value for optional command-arguments ([#1508]) - supports custom processing function ([#1508]) - `.createArgument()` factory method ([#1497]) - `.addArgument()` ([#1490]) - `Argument` supports `.choices()` ([#1525]) - `.showHelpAfterError()` to display full help or a custom message after an error ([#1534]) - `.hook()` with support for `'preAction'` and `'postAction'` callbacks ([#1514]) - client typing of `.opts()` return type using TypeScript generics ([#1539]) - the number of command-arguments is checked for programs without an action handler ([#1502]) - `.getOptionValue()` and `.setOptionValue()` ([#1521]) ### Changed - refactor and simplify TypeScript declarations (with no default export) ([#1520]) - `.parseAsync()` is now declared as `async` ([#1513]) - *Breaking:* `Help` method `.visibleArguments()` returns array of `Argument` ([#1490]) - *Breaking:* Commander 8 requires Node.js 12 or higher ([#1500]) - *Breaking:* `CommanderError` code `commander.invalidOptionArgument` renamed `commander.invalidArgument` ([#1508]) - *Breaking:* TypeScript declaration for `.addTextHelp()` callback no longer allows result of `undefined`, now just `string` ([#1516]) - refactor `index.tab` into a file per class ([#1522]) - remove help suggestion from "unknown command" error message (see `.showHelpAfteError()`) ([#1534]) - `Command` property `.arg` initialised to empty array (was previously undefined) ([#1529]) - update dependencies ### Deprecated - second parameter of `cmd.description(desc, argDescriptions)` for adding argument descriptions ([#1490]) - (use new `.argument(name, description)` instead) - `InvalidOptionArgumentError` (replaced by `InvalidArgumentError`) ([#1508]) ### Removed - *Breaking:* TypeScript declaration for default export of global `Command` object ([#1520]) - (still available as named `program` export) ### Migration Tips If you have a simple program without an action handler, you will now get an error if there are missing command-arguments. ```js program .option('-d, --debug') .arguments(''); program.parse(); ``` ```sh $ node trivial.js error: missing required argument 'file' ``` If you want to show the help in this situation, you could check the arguments before parsing: ```js if (process.argv.length === 2) program.help(); program.parse(); ``` Or, you might choose to show the help after any user error: ```js program.showHelpAfterError(); ``` ## [8.0.0-2] (2021-06-06) (Released in 8.0.0) ## [8.0.0-1] (2021-05-30) (Released in 8.0.0) ## [8.0.0-0] (2021-05-23) (Released in 8.0.0) ## [7.2.0] (2021-03-22) ### Added - TypeScript typing for `parent` property on `Command` ([#1475]) - TypeScript typing for `.attributeName()` on `Option` ([#1483]) - support information in package ([#1477]) ### Changed - improvements to error messages, README, and tests - update dependencies ## [7.1.0] (2021-02-15) ### Added - support for named imports from ECMAScript modules ([#1440]) - add `.cjs` to list of expected script file extensions ([#1449]) - allow using option choices and variadic together ([#1454]) ### Fixed - replace use of deprecated `process.mainModule` ([#1448]) - regression for legacy `command('*')` and call when command line includes options ([#1464]) - regression for `on('command:*', ...)` and call when command line includes unknown options ([#1464]) - display best error for combination of unknown command and unknown option (i.e. unknown command) ([#1464]) ### Changed - make TypeScript typings tests stricter ([#1453]) - improvements to README and tests ## [7.0.0] (2021-01-15) ### Added - `.enablePositionalOptions()` to let program and subcommand reuse same option ([#1427]) - `.passThroughOptions()` to pass options through to other programs without needing `--` ([#1427]) - `.allowExcessArguments(false)` to show an error message if there are too many command-arguments on command line for the action handler ([#1409]) - `.configureOutput()` to modify use of stdout and stderr or customise display of errors ([#1387]) - use `.addHelpText()` to add text before or after the built-in help, for just current command or also for all subcommands ([#1296]) - enhance Option class ([#1331]) - allow hiding options from help - allow restricting option arguments to a list of choices - allow setting how default value is shown in help - `.createOption()` to support subclassing of automatically created options (like `.createCommand()`) ([#1380]) - refactor the code generating the help into a separate public Help class ([#1365]) - support sorting subcommands and options in help - support specifying wrap width (columns) - allow subclassing Help class - allow configuring Help class without subclassing ### Changed - *Breaking:* options are stored safely by default, not as properties on the command ([#1409]) - this especially affects accessing options on program, use `program.opts()` - revert behaviour with `.storeOptionsAsProperties()` - *Breaking:* action handlers are passed options and command separately ([#1409]) - deprecated callback parameter to `.help()` and `.outputHelp()` (removed from README) ([#1296]) - *Breaking:* errors now displayed using `process.stderr.write()` instead of `console.error()` - deprecate `.on('--help')` (removed from README) ([#1296]) - initialise the command description to empty string (previously undefined) ([#1365]) - document and annotate deprecated routines ([#1349]) ### Fixed - wrapping bugs in help ([#1365]) - first line of command description was wrapping two characters early - pad width calculation was not including help option and help command - pad width calculation was including hidden options and commands - improve backwards compatibility for custom command event listeners ([#1403]) ### Deleted - *Breaking:* `.passCommandToAction()` ([#1409]) - no longer needed as action handler is passed options and command - *Breaking:* "extra arguments" parameter to action handler ([#1409]) - if being used to detect excess arguments, there is now an error available by setting `.allowExcessArguments(false)` ### Migration Tips The biggest change is the parsed option values. Previously the options were stored by default as properties on the command object, and now the options are stored separately. If you wish to restore the old behaviour and get running quickly you can call `.storeOptionsAsProperties()`. To allow you to move to the new code patterns incrementally, the action handler will be passed the command _twice_, to match the new "options" and "command" parameters (see below). **program options** Use the `.opts()` method to access the options. This is available on any command but is used most with the program. ```js program.option('-d, --debug'); program.parse(); // Old code before Commander 7 if (program.debug) console.log(`Program name is ${program.name()}`); ``` ```js // New code const options = program.opts(); if (options.debug) console.log(`Program name is ${program.name()}`); ``` **action handler** The action handler gets passed a parameter for each command-argument you declared. Previously by default the next parameter was the command object with the options as properties. Now the next two parameters are instead the options and the command. If you only accessed the options there may be no code changes required. ```js program .command('compress ') .option('-t, --trace') // Old code before Commander 7 .action((filename, cmd)) => { if (cmd.trace) console.log(`Command name is ${cmd.name()}`); }); ``` ```js // New code .action((filename, options, command)) => { if (options.trace) console.log(`Command name is ${command.name()}`); }); ``` If you already set `.storeOptionsAsProperties(false)` you may still need to adjust your code. ```js program .command('compress ') .storeOptionsAsProperties(false) .option('-t, --trace') // Old code before Commander 7 .action((filename, command)) => { if (command.opts().trace) console.log(`Command name is ${command.name()}`); }); ``` ```js // New code .action((filename, options, command)) => { if (command.opts().trace) console.log(`Command name is ${command.name()}`); }); ``` ## [7.0.0-2] (2020-12-14) (Released in 7.0.0) ## [7.0.0-1] (2020-11-21) (Released in 7.0.0) ## [7.0.0-0] (2020-10-25) (Released in 7.0.0) ## [6.2.1] (2020-12-13) ### Fixed - some tests failed if directory path included a space ([1390]) ## [6.2.0] (2020-10-25) ### Added - added 'tsx' file extension for stand-alone executable subcommands ([#1368]) - documented second parameter to `.description()` to describe command arguments ([#1353]) - documentation of special cases with options taking varying numbers of option-arguments ([#1332]) - documentation for terminology ([#1361]) ### Fixed - add missing TypeScript definition for `.addHelpCommand()' ([#1375]) - removed blank line after "Arguments:" in help, to match "Options:" and "Commands:" ([#1360]) ### Changed - update dependencies ## [6.1.0] (2020-08-28) ### Added - include URL to relevant section of README for error for potential conflict between Command properties and option values ([#1306]) - `.combineFlagAndOptionalValue(false)` to ease upgrade path from older versions of Commander ([#1326]) - allow disabling the built-in help option using `.helpOption(false)` ([#1325]) - allow just some arguments in `argumentDescription` to `.description()` ([#1323]) ### Changed - tidy async test and remove lint override ([#1312]) ### Fixed - executable subcommand launching when script path not known ([#1322]) ## [6.0.0] (2020-07-21) ### Added - add support for variadic options ([#1250]) - allow options to be added with just a short flag ([#1256]) - *Breaking* the option property has same case as flag. e.g. flag `-n` accessed as `opts().n` (previously uppercase) - *Breaking* throw an error if there might be a clash between option name and a Command property, with advice on how to resolve ([#1275]) ### Fixed - Options which contain -no- in the middle of the option flag should not be treated as negatable. ([#1301]) ## [6.0.0-0] (2020-06-20) (Released in 6.0.0) ## [5.1.0] (2020-04-25) ### Added - support for multiple command aliases, the first of which is shown in the auto-generated help ([#531], [#1236]) - configuration support in `addCommand()` for `hidden` and `isDefault` ([#1232]) ### Fixed - omit masked help flags from the displayed help ([#645], [#1247]) - remove old short help flag when change help flags using `helpOption` ([#1248]) ### Changed - remove use of `arguments` to improve auto-generated help in editors ([#1235]) - rename `.command()` configuration `noHelp` to `hidden` (but not remove old support) ([#1232]) - improvements to documentation - update dependencies - update tested versions of node - eliminate lint errors in TypeScript ([#1208]) ## [5.0.0] (2020-03-14) ### Added * support for nested commands with action-handlers ([#1] [#764] [#1149]) * `.addCommand()` for adding a separately configured command ([#764] [#1149]) * allow a non-executable to be set as the default command ([#742] [#1149]) * implicit help command when there are subcommands (previously only if executables) ([#1149]) * customise implicit help command with `.addHelpCommand()` ([#1149]) * display error message for unknown subcommand, by default ([#432] [#1088] [#1149]) * display help for missing subcommand, by default ([#1088] [#1149]) * combined short options as single argument may include boolean flags and value flag and value (e.g. `-a -b -p 80` can be written as `-abp80`) ([#1145]) * `.parseOption()` includes short flag and long flag expansions ([#1145]) * `.helpInformation()` returns help text as a string, previously a private routine ([#1169]) * `.parse()` implicitly uses `process.argv` if arguments not specified ([#1172]) * optionally specify where `.parse()` arguments "from", if not following node conventions ([#512] [#1172]) * suggest help option along with unknown command error ([#1179]) * TypeScript definition for `commands` property of `Command` ([#1184]) * export `program` property ([#1195]) * `createCommand` factory method to simplify subclassing ([#1191]) ### Fixed * preserve argument order in subcommands ([#508] [#962] [#1138]) * do not emit `command:*` for executable subcommands ([#809] [#1149]) * action handler called whether or not there are non-option arguments ([#1062] [#1149]) * combining option short flag and value in single argument now works for subcommands ([#1145]) * only add implicit help command when it will not conflict with other uses of argument ([#1153] [#1149]) * implicit help command works with command aliases ([#948] [#1149]) * options are validated whether or not there is an action handler ([#1149]) ### Changed * *Breaking* `.args` contains command arguments with just recognised options removed ([#1032] [#1138]) * *Breaking* display error if required argument for command is missing ([#995] [#1149]) * tighten TypeScript definition of custom option processing function passed to `.option()` ([#1119]) * *Breaking* `.allowUnknownOption()` ([#802] [#1138]) * unknown options included in arguments passed to command action handler * unknown options included in `.args` * only recognised option short flags and long flags are expanded (e.g. `-ab` or `--foo=bar`) ([#1145]) * *Breaking* `.parseOptions()` ([#1138]) * `args` in returned result renamed `operands` and does not include anything after first unknown option * `unknown` in returned result has arguments after first unknown option including operands, not just options and values * *Breaking* `.on('command:*', callback)` and other command events passed (changed) results from `.parseOptions`, i.e. operands and unknown ([#1138]) * refactor Option from prototype to class ([#1133]) * refactor Command from prototype to class ([#1159]) * changes to error handling ([#1165]) * throw for author error, not just display message * preflight for variadic error * add tips to missing subcommand executable * TypeScript fluent return types changed to be more subclass friendly, return `this` rather than `Command` ([#1180]) * `.parseAsync` returns `Promise` to be consistent with `.parse()` ([#1180]) * update dependencies ### Removed * removed EventEmitter from TypeScript definition for Command, eliminating implicit peer dependency on `@types/node` ([#1146]) * removed private function `normalize` (the functionality has been integrated into `parseOptions`) ([#1145]) * `parseExpectedArgs` is now private ([#1149]) ### Migration Tips If you use `.on('command:*')` or more complicated tests to detect an unrecognised subcommand, you may be able to delete the code and rely on the default behaviour. If you use `program.args` or more complicated tests to detect a missing subcommand, you may be able to delete the code and rely on the default behaviour. If you use `.command('*')` to add a default command, you may be be able to switch to `isDefault:true` with a named command. If you want to continue combining short options with optional values as though they were boolean flags, set `combineFlagAndOptionalValue(false)` to expand `-fb` to `-f -b` rather than `-f b`. ## [5.0.0-4] (2020-03-03) (Released in 5.0.0) ## [5.0.0-3] (2020-02-20) (Released in 5.0.0) ## [5.0.0-2] (2020-02-10) (Released in 5.0.0) ## [5.0.0-1] (2020-02-08) (Released in 5.0.0) ## [5.0.0-0] (2020-02-02) (Released in 5.0.0) ## [4.1.1] (2020-02-02) ### Fixed * TypeScript definition for `.action()` should include Promise for async ([#1157]) ## [4.1.0] (2020-01-06) ### Added * two routines to change how option values are handled, and eliminate name clashes with command properties ([#933] [#1102]) * see storeOptionsAsProperties and passCommandToAction in README * `.parseAsync` to use instead of `.parse` if supply async action handlers ([#806] [#1118]) ### Fixed * Remove trailing blanks from wrapped help text ([#1096]) ### Changed * update dependencies * extend security coverage for Commander 2.x to 2020-02-03 * improvements to README * improvements to TypeScript definition documentation * move old versions out of main CHANGELOG * removed explicit use of `ts-node` in tests ## [4.0.1] (2019-11-12) ### Fixed * display help when requested, even if there are missing required options ([#1091]) ## [4.0.0] (2019-11-02) ### Added * automatically wrap and indent help descriptions for options and commands ([#1051]) * `.exitOverride()` allows override of calls to `process.exit` for additional error handling and to keep program running ([#1040]) * support for declaring required options with `.requiredOptions()` ([#1071]) * GitHub Actions support ([#1027]) * translation links in README ### Changed * dev: switch tests from Sinon+Should to Jest with major rewrite of tests ([#1035]) * call default subcommand even when there are unknown options ([#1047]) * *Breaking* Commander is only officially supported on Node 8 and above, and requires Node 6 ([#1053]) ### Fixed * *Breaking* keep command object out of program.args when action handler called ([#1048]) * also, action handler now passed array of unknown arguments * complain about unknown options when program argument supplied and action handler ([#1049]) * this changes parameters to `command:*` event to include unknown arguments * removed deprecated `customFds` option from call to `child_process.spawn` ([#1052]) * rework TypeScript declarations to bring all types into imported namespace ([#1081]) ### Migration Tips #### Testing for no arguments If you were previously using code like: ```js if (!program.args.length) ... ``` a partial replacement is: ```js if (program.rawArgs.length < 3) ... ``` ## [4.0.0-1] Prerelease (2019-10-08) (Released in 4.0.0) ## [4.0.0-0] Prerelease (2019-10-01) (Released in 4.0.0) ## [3.0.2] (2019-09-27) ### Fixed * Improve tracking of executable subcommands. ### Changed * update development dependencies ## [3.0.1] (2019-08-30) ### Added * .name and .usage to README ([#1010]) * Table of Contents to README ([#1010]) * TypeScript definition for `executableFile` in CommandOptions ([#1028]) ### Changed * consistently use `const` rather than `var` in README ([#1026]) ### Fixed * help for sub commands with custom executableFile ([#1018]) ## [3.0.0] / 2019-08-08 * Add option to specify executable file name ([#999]) * e.g. `.command('clone', 'clone description', { executableFile: 'myClone' })` * Change docs for `.command` to contrast action handler vs git-style executable. ([#938] [#990]) * **Breaking** Change TypeScript to use overloaded function for `.command`. ([#938] [#990]) * Change to use straight quotes around strings in error messages (like 'this' instead of `this') ([#915]) * Add TypeScript "reference types" for node ([#974]) * Add support for hyphen as an option argument in subcommands ([#697]) * Add support for a short option flag and its value to be concatenated for action handler subcommands ([#599]) * e.g. `-p 80` can also be supplied as `-p80` * Add executable arguments to spawn in win32, for git-style executables ([#611]) * e.g. `node --harmony myCommand.js clone` * Add parent command as prefix of subcommand in help ([#980]) * Add optional custom description to `.version` ([#963]) * e.g. `program.version('0.0.1', '-v, --vers', 'output the current version')` * Add `.helpOption(flags, description)` routine to customise help flags and description ([#963]) * e.g. `.helpOption('-e, --HELP', 'read more information')` * Fix behavior of --no-* options ([#795]) * can now define both `--foo` and `--no-foo` * **Breaking** custom event listeners: `--no-foo` on cli now emits `option:no-foo` (previously `option:foo`) * **Breaking** default value: defining `--no-foo` after defining `--foo` leaves the default value unchanged (previously set it to false) * allow boolean default value, such as from environment ([#987]) * Increment inspector port for spawned subcommands ([#991]) * e.g. `node --inspect myCommand.js clone` ### Migration Tips The custom event for a negated option like `--no-foo` is `option:no-foo` (previously `option:foo`). ```js program .option('--no-foo') .on('option:no-foo', () => { console.log('removing foo'); }); ``` When using TypeScript, adding a command does not allow an explicit `undefined` for an unwanted executable description (e.g for a command with an action handler). ```js program .command('action1', undefined, { noHelp: true }) // No longer valid .command('action2', { noHelp: true }) // Correct ``` ## 3.0.0-0 Prerelease / 2019-07-28 (Released as 3.0.0) ## [2.20.1] (2019-09-29) ### Fixed * Improve tracking of executable subcommands. ### Changed * update development dependencies ## 2.20.0 / 2019-04-02 * fix: resolve symbolic links completely when hunting for subcommands (#935) * Update index.d.ts (#930) * Update Readme.md (#924) * Remove --save option as it isn't required anymore (#918) * Add link to the license file (#900) * Added example of receiving args from options (#858) * Added missing semicolon (#882) * Add extension to .eslintrc (#876) ## 2.19.0 / 2018-10-02 * Removed newline after Options and Commands headers (#864) * Bugfix - Error output (#862) * Fix to change default value to string (#856) ## 2.18.0 / 2018-09-07 * Standardize help output (#853) * chmod 644 travis.yml (#851) * add support for execute typescript subcommand via ts-node (#849) ## 2.17.1 / 2018-08-07 * Fix bug in command emit (#844) ## 2.17.0 / 2018-08-03 * fixed newline output after help information (#833) * Fix to emit the action even without command (#778) * npm update (#823) ## 2.16.0 / 2018-06-29 * Remove Makefile and `test/run` (#821) * Make 'npm test' run on Windows (#820) * Add badge to display install size (#807) * chore: cache node_modules (#814) * chore: remove Node.js 4 (EOL), add Node.js 10 (#813) * fixed typo in readme (#812) * Fix types (#804) * Update eslint to resolve vulnerabilities in lodash (#799) * updated readme with custom event listeners. (#791) * fix tests (#794) ## 2.15.0 / 2018-03-07 * Update downloads badge to point to graph of downloads over time instead of duplicating link to npm * Arguments description ## 2.14.1 / 2018-02-07 * Fix typing of help function ## 2.14.0 / 2018-02-05 * only register the option:version event once * Fixes issue #727: Passing empty string for option on command is set to undefined * enable eqeqeq rule * resolves #754 add linter configuration to project * resolves #560 respect custom name for version option * document how to override the version flag * document using options per command ## 2.13.0 / 2018-01-09 * Do not print default for --no- * remove trailing spaces in command help * Update CI's Node.js to LTS and latest version * typedefs: Command and Option types added to commander namespace ## 2.12.2 / 2017-11-28 * fix: typings are not shipped ## 2.12.1 / 2017-11-23 * Move @types/node to dev dependency ## 2.12.0 / 2017-11-22 * add attributeName() method to Option objects * Documentation updated for options with --no prefix * typings: `outputHelp` takes a string as the first parameter * typings: use overloads * feat(typings): update to match js api * Print default value in option help * Fix translation error * Fail when using same command and alias (#491) * feat(typings): add help callback * fix bug when description is add after command with options (#662) * Format js code * Rename History.md to CHANGELOG.md (#668) * feat(typings): add typings to support TypeScript (#646) * use current node ## 2.11.0 / 2017-07-03 * Fix help section order and padding (#652) * feature: support for signals to subcommands (#632) * Fixed #37, --help should not display first (#447) * Fix translation errors. (#570) * Add package-lock.json * Remove engines * Upgrade package version * Prefix events to prevent conflicts between commands and options (#494) * Removing dependency on graceful-readlink * Support setting name in #name function and make it chainable * Add .vscode directory to .gitignore (Visual Studio Code metadata) * Updated link to ruby commander in readme files ## 2.10.0 / 2017-06-19 * Update .travis.yml. drop support for older node.js versions. * Fix require arguments in README.md * On SemVer you do not start from 0.0.1 * Add missing semi colon in readme * Add save param to npm install * node v6 travis test * Update Readme_zh-CN.md * Allow literal '--' to be passed-through as an argument * Test subcommand alias help * link build badge to master branch * Support the alias of Git style sub-command * added keyword commander for better search result on npm * Fix Sub-Subcommands * test node.js stable * Fixes TypeError when a command has an option called `--description` * Update README.md to make it beginner friendly and elaborate on the difference between angled and square brackets. * Add chinese Readme file ## 2.9.0 / 2015-10-13 * Add option `isDefault` to set default subcommand #415 @Qix- * Add callback to allow filtering or post-processing of help text #434 @djulien * Fix `undefined` text in help information close #414 #416 @zhiyelee ## 2.8.1 / 2015-04-22 * Back out `support multiline description` Close #396 #397 ## 2.8.0 / 2015-04-07 * Add `process.execArg` support, execution args like `--harmony` will be passed to sub-commands #387 @DigitalIO @zhiyelee * Fix bug in Git-style sub-commands #372 @zhiyelee * Allow commands to be hidden from help #383 @tonylukasavage * When git-style sub-commands are in use, yet none are called, display help #382 @claylo * Add ability to specify arguments syntax for top-level command #258 @rrthomas * Support multiline descriptions #208 @zxqfox ## 2.7.1 / 2015-03-11 * Revert #347 (fix collisions when option and first arg have same name) which causes a bug in #367. ## 2.7.0 / 2015-03-09 * Fix git-style bug when installed globally. Close #335 #349 @zhiyelee * Fix collisions when option and first arg have same name. Close #346 #347 @tonylukasavage * Add support for camelCase on `opts()`. Close #353 @nkzawa * Add node.js 0.12 and io.js to travis.yml * Allow RegEx options. #337 @palanik * Fixes exit code when sub-command failing. Close #260 #332 @pirelenito * git-style `bin` files in $PATH make sense. Close #196 #327 @zhiyelee ## 2.6.0 / 2014-12-30 * added `Command#allowUnknownOption` method. Close #138 #318 @doozr @zhiyelee * Add application description to the help msg. Close #112 @dalssoft ## 2.5.1 / 2014-12-15 * fixed two bugs incurred by variadic arguments. Close #291 @Quentin01 #302 @zhiyelee ## 2.5.0 / 2014-10-24 * add support for variadic arguments. Closes #277 @whitlockjc ## 2.4.0 / 2014-10-17 * fixed a bug on executing the coercion function of subcommands option. Closes #270 * added `Command.prototype.name` to retrieve command name. Closes #264 #266 @tonylukasavage * added `Command.prototype.opts` to retrieve all the options as a simple object of key-value pairs. Closes #262 @tonylukasavage * fixed a bug on subcommand name. Closes #248 @jonathandelgado * fixed function normalize doesn’t honor option terminator. Closes #216 @abbr ## 2.3.0 / 2014-07-16 * add command alias'. Closes PR #210 * fix: Typos. Closes #99 * fix: Unused fs module. Closes #217 ## 2.2.0 / 2014-03-29 * add passing of previous option value * fix: support subcommands on windows. Closes #142 * Now the defaultValue passed as the second argument of the coercion function. ## 2.1.0 / 2013-11-21 * add: allow cflag style option params, unit test, fixes #174 ## 2.0.0 / 2013-07-18 * remove input methods (.prompt, .confirm, etc) ## 0.6.1 / 2012-06-01 * Added: append (yes or no) on confirmation * Added: allow node.js v0.7.x ## 0.6.0 / 2012-04-10 * Added `.prompt(obj, callback)` support. Closes #49 * Added default support to .choose(). Closes #41 * Fixed the choice example ## 0.5.1 / 2011-12-20 * Fixed `password()` for recent nodes. Closes #36 ## 0.5.0 / 2011-12-04 * Added sub-command option support [itay] ## 0.4.3 / 2011-12-04 * Fixed custom help ordering. Closes #32 ## 0.4.2 / 2011-11-24 * Added travis support * Fixed: line-buffered input automatically trimmed. Closes #31 ## 0.4.1 / 2011-11-18 * Removed listening for "close" on --help ## 0.4.0 / 2011-11-15 * Added support for `--`. Closes #24 ## 0.3.3 / 2011-11-14 * Fixed: wait for close event when writing help info [Jerry Hamlet] ## 0.3.2 / 2011-11-01 * Fixed long flag definitions with values [felixge] ## 0.3.1 / 2011-10-31 * Changed `--version` short flag to `-V` from `-v` * Changed `.version()` so it's configurable [felixge] ## 0.3.0 / 2011-10-31 * Added support for long flags only. Closes #18 ## 0.2.1 / 2011-10-24 * "node": ">= 0.4.x < 0.7.0". Closes #20 ## 0.2.0 / 2011-09-26 * Allow for defaults that are not just boolean. Default peassignment only occurs for --no-*, optional, and required arguments. [Jim Isaacs] ## 0.1.0 / 2011-08-24 * Added support for custom `--help` output ## 0.0.5 / 2011-08-18 * Changed: when the user enters nothing prompt for password again * Fixed issue with passwords beginning with numbers [NuckChorris] ## 0.0.4 / 2011-08-15 * Fixed `Commander#args` ## 0.0.3 / 2011-08-15 * Added default option value support ## 0.0.2 / 2011-08-15 * Added mask support to `Command#password(str[, mask], fn)` * Added `Command#password(str, fn)` ## 0.0.1 / 2010-01-03 * Initial release [#948]: https://github.com/tj/commander.js/issues/948 [#1032]: https://github.com/tj/commander.js/issues/1032 [#1250]: https://github.com/tj/commander.js/pull/1250 [#1256]: https://github.com/tj/commander.js/pull/1256 [#1275]: https://github.com/tj/commander.js/pull/1275 [#1296]: https://github.com/tj/commander.js/pull/1296 [#1301]: https://github.com/tj/commander.js/issues/1301 [#1306]: https://github.com/tj/commander.js/pull/1306 [#1312]: https://github.com/tj/commander.js/pull/1312 [#1322]: https://github.com/tj/commander.js/pull/1322 [#1323]: https://github.com/tj/commander.js/pull/1323 [#1325]: https://github.com/tj/commander.js/pull/1325 [#1326]: https://github.com/tj/commander.js/pull/1326 [#1331]: https://github.com/tj/commander.js/pull/1331 [#1332]: https://github.com/tj/commander.js/pull/1332 [#1349]: https://github.com/tj/commander.js/pull/1349 [#1353]: https://github.com/tj/commander.js/pull/1353 [#1360]: https://github.com/tj/commander.js/pull/1360 [#1361]: https://github.com/tj/commander.js/pull/1361 [#1365]: https://github.com/tj/commander.js/pull/1365 [#1368]: https://github.com/tj/commander.js/pull/1368 [#1375]: https://github.com/tj/commander.js/pull/1375 [#1380]: https://github.com/tj/commander.js/pull/1380 [#1387]: https://github.com/tj/commander.js/pull/1387 [#1390]: https://github.com/tj/commander.js/pull/1390 [#1403]: https://github.com/tj/commander.js/pull/1403 [#1409]: https://github.com/tj/commander.js/pull/1409 [#1427]: https://github.com/tj/commander.js/pull/1427 [#1440]: https://github.com/tj/commander.js/pull/1440 [#1448]: https://github.com/tj/commander.js/pull/1448 [#1449]: https://github.com/tj/commander.js/pull/1449 [#1453]: https://github.com/tj/commander.js/pull/1453 [#1454]: https://github.com/tj/commander.js/pull/1454 [#1464]: https://github.com/tj/commander.js/pull/1464 [#1475]: https://github.com/tj/commander.js/pull/1475 [#1477]: https://github.com/tj/commander.js/pull/1477 [#1483]: https://github.com/tj/commander.js/pull/1483 [#1490]: https://github.com/tj/commander.js/pull/1490 [#1497]: https://github.com/tj/commander.js/pull/1497 [#1500]: https://github.com/tj/commander.js/pull/1500 [#1508]: https://github.com/tj/commander.js/pull/1508 [#1513]: https://github.com/tj/commander.js/pull/1513 [#1514]: https://github.com/tj/commander.js/pull/1514 [#1516]: https://github.com/tj/commander.js/pull/1516 [#1520]: https://github.com/tj/commander.js/pull/1520 [#1521]: https://github.com/tj/commander.js/pull/1521 [#1522]: https://github.com/tj/commander.js/pull/1522 [#1525]: https://github.com/tj/commander.js/pull/1525 [#1529]: https://github.com/tj/commander.js/pull/1529 [#1534]: https://github.com/tj/commander.js/pull/1534 [#1539]: https://github.com/tj/commander.js/pull/1539 [#1557]: https://github.com/tj/commander.js/pull/1557 [#1567]: https://github.com/tj/commander.js/pull/1567 [#1570]: https://github.com/tj/commander.js/pull/1570 [#1571]: https://github.com/tj/commander.js/pull/1571 [#1587]: https://github.com/tj/commander.js/pull/1587 [#1589]: https://github.com/tj/commander.js/pull/1589 [#1590]: https://github.com/tj/commander.js/pull/1590 [#1612]: https://github.com/tj/commander.js/pull/1612 [#1613]: https://github.com/tj/commander.js/pull/1613 [#1652]: https://github.com/tj/commander.js/pull/1652 [#1655]: https://github.com/tj/commander.js/pull/1655 [#1657]: https://github.com/tj/commander.js/pull/1657 [#1659]: https://github.com/tj/commander.js/pull/1659 [#1667]: https://github.com/tj/commander.js/pull/1667 [#1669]: https://github.com/tj/commander.js/pull/1669 [#1671]: https://github.com/tj/commander.js/pull/1671 [#1675]: https://github.com/tj/commander.js/pull/1675 [#1]: https://github.com/tj/commander.js/issues/1 [#432]: https://github.com/tj/commander.js/issues/432 [#508]: https://github.com/tj/commander.js/issues/508 [#512]: https://github.com/tj/commander.js/issues/512 [#531]: https://github.com/tj/commander.js/issues/531 [#645]: https://github.com/tj/commander.js/issues/645 [#742]: https://github.com/tj/commander.js/issues/742 [#764]: https://github.com/tj/commander.js/issues/764 [#802]: https://github.com/tj/commander.js/issues/802 [#809]: https://github.com/tj/commander.js/issues/809 [#962]: https://github.com/tj/commander.js/issues/962 [#995]: https://github.com/tj/commander.js/issues/995 [#1062]: https://github.com/tj/commander.js/pull/1062 [#1088]: https://github.com/tj/commander.js/issues/1088 [#1119]: https://github.com/tj/commander.js/pull/1119 [#1133]: https://github.com/tj/commander.js/pull/1133 [#1138]: https://github.com/tj/commander.js/pull/1138 [#1145]: https://github.com/tj/commander.js/pull/1145 [#1146]: https://github.com/tj/commander.js/pull/1146 [#1149]: https://github.com/tj/commander.js/pull/1149 [#1153]: https://github.com/tj/commander.js/issues/1153 [#1159]: https://github.com/tj/commander.js/pull/1159 [#1165]: https://github.com/tj/commander.js/pull/1165 [#1169]: https://github.com/tj/commander.js/pull/1169 [#1172]: https://github.com/tj/commander.js/pull/1172 [#1179]: https://github.com/tj/commander.js/pull/1179 [#1180]: https://github.com/tj/commander.js/pull/1180 [#1184]: https://github.com/tj/commander.js/pull/1184 [#1191]: https://github.com/tj/commander.js/pull/1191 [#1195]: https://github.com/tj/commander.js/pull/1195 [#1208]: https://github.com/tj/commander.js/pull/1208 [#1232]: https://github.com/tj/commander.js/pull/1232 [#1235]: https://github.com/tj/commander.js/pull/1235 [#1236]: https://github.com/tj/commander.js/pull/1236 [#1247]: https://github.com/tj/commander.js/pull/1247 [#1248]: https://github.com/tj/commander.js/pull/1248 [#1027]: https://github.com/tj/commander.js/pull/1027 [#1035]: https://github.com/tj/commander.js/pull/1035 [#1040]: https://github.com/tj/commander.js/pull/1040 [#1047]: https://github.com/tj/commander.js/pull/1047 [#1048]: https://github.com/tj/commander.js/pull/1048 [#1049]: https://github.com/tj/commander.js/pull/1049 [#1051]: https://github.com/tj/commander.js/pull/1051 [#1052]: https://github.com/tj/commander.js/pull/1052 [#1053]: https://github.com/tj/commander.js/pull/1053 [#1071]: https://github.com/tj/commander.js/pull/1071 [#1081]: https://github.com/tj/commander.js/pull/1081 [#1091]: https://github.com/tj/commander.js/pull/1091 [#1096]: https://github.com/tj/commander.js/pull/1096 [#1102]: https://github.com/tj/commander.js/pull/1102 [#1118]: https://github.com/tj/commander.js/pull/1118 [#1157]: https://github.com/tj/commander.js/pull/1157 [#806]: https://github.com/tj/commander.js/issues/806 [#599]: https://github.com/tj/commander.js/issues/599 [#611]: https://github.com/tj/commander.js/issues/611 [#697]: https://github.com/tj/commander.js/issues/697 [#795]: https://github.com/tj/commander.js/issues/795 [#915]: https://github.com/tj/commander.js/issues/915 [#938]: https://github.com/tj/commander.js/issues/938 [#963]: https://github.com/tj/commander.js/issues/963 [#974]: https://github.com/tj/commander.js/issues/974 [#980]: https://github.com/tj/commander.js/issues/980 [#987]: https://github.com/tj/commander.js/issues/987 [#990]: https://github.com/tj/commander.js/issues/990 [#991]: https://github.com/tj/commander.js/issues/991 [#999]: https://github.com/tj/commander.js/issues/999 [#1010]: https://github.com/tj/commander.js/pull/1010 [#1018]: https://github.com/tj/commander.js/pull/1018 [#1026]: https://github.com/tj/commander.js/pull/1026 [#1028]: https://github.com/tj/commander.js/pull/1028 [Unreleased]: https://github.com/tj/commander.js/compare/master...develop [9.0.0]: https://github.com/tj/commander.js/compare/v8.3.0...v9.0.0 [9.0.0-1]: https://github.com/tj/commander.js/compare/v9.0.0-0...v9.0.0-1 [9.0.0-0]: https://github.com/tj/commander.js/compare/v8.3.0...v9.0.0-0 [8.3.0]: https://github.com/tj/commander.js/compare/v8.2.0...v8.3.0 [8.2.0]: https://github.com/tj/commander.js/compare/v8.1.0...v8.2.0 [8.1.0]: https://github.com/tj/commander.js/compare/v8.0.0...v8.1.0 [8.0.0]: https://github.com/tj/commander.js/compare/v7.2.0...v8.0.0 [8.0.0-2]: https://github.com/tj/commander.js/compare/v8.0.0-1...v8.0.0-2 [8.0.0-1]: https://github.com/tj/commander.js/compare/v8.0.0-0...v8.0.0-1 [8.0.0-0]: https://github.com/tj/commander.js/compare/v7.2.0...v8.0.0-0 [7.2.0]: https://github.com/tj/commander.js/compare/v7.1.0...v7.2.0 [7.1.0]: https://github.com/tj/commander.js/compare/v7.0.0...v7.1.0 [7.0.0]: https://github.com/tj/commander.js/compare/v6.2.1...v7.0.0 [7.0.0-2]: https://github.com/tj/commander.js/compare/v7.0.0-1...v7.0.0-2 [7.0.0-1]: https://github.com/tj/commander.js/compare/v7.0.0-0...v7.0.0-1 [7.0.0-0]: https://github.com/tj/commander.js/compare/v6.2.0...v7.0.0-0 [6.2.1]: https://github.com/tj/commander.js/compare/v6.2.0..v6.2.1 [6.2.0]: https://github.com/tj/commander.js/compare/v6.1.0..v6.2.0 [6.1.0]: https://github.com/tj/commander.js/compare/v6.0.0..v6.1.0 [6.0.0]: https://github.com/tj/commander.js/compare/v5.1.0..v6.0.0 [6.0.0-0]: https://github.com/tj/commander.js/compare/v5.1.0..v6.0.0-0 [5.1.0]: https://github.com/tj/commander.js/compare/v5.0.0..v5.1.0 [5.0.0]: https://github.com/tj/commander.js/compare/v4.1.1..v5.0.0 [5.0.0-4]: https://github.com/tj/commander.js/compare/v5.0.0-3..v5.0.0-4 [5.0.0-3]: https://github.com/tj/commander.js/compare/v5.0.0-2..v5.0.0-3 [5.0.0-2]: https://github.com/tj/commander.js/compare/v5.0.0-1..v5.0.0-2 [5.0.0-1]: https://github.com/tj/commander.js/compare/v5.0.0-0..v5.0.0-1 [5.0.0-0]: https://github.com/tj/commander.js/compare/v4.1.1..v5.0.0-0 [4.1.1]: https://github.com/tj/commander.js/compare/v4.1.0..v4.1.1 [4.1.0]: https://github.com/tj/commander.js/compare/v4.0.1..v4.1.0 [4.0.1]: https://github.com/tj/commander.js/compare/v4.0.0..v4.0.1 [4.0.0]: https://github.com/tj/commander.js/compare/v3.0.2..v4.0.0 [4.0.0-1]: https://github.com/tj/commander.js/compare/v4.0.0-0..v4.0.0-1 [4.0.0-0]: https://github.com/tj/commander.js/compare/v3.0.2...v4.0.0-0 [3.0.2]: https://github.com/tj/commander.js/compare/v3.0.1...v3.0.2 [3.0.1]: https://github.com/tj/commander.js/compare/v3.0.0...v3.0.1 [3.0.0]: https://github.com/tj/commander.js/compare/v2.20.1...v3.0.0 [2.20.1]: https://github.com/tj/commander.js/compare/v2.20.0...v2.20.1 commander.js-9.0.0/CONTRIBUTING.md000066400000000000000000000033061417504050400163330ustar00rootroot00000000000000# Contributing ## Issues New issues are welcome, whether questions or suggestions or reporting bugs. You are also welcome to contribute by adding helpful comments on an existing issue. We love reproducible code examples in questions and answers. If you get a satisfactory reply to a question then please close your issue, but it is ok to leave an issue open for more replies or interest. Inactive issues may get closed after one month if they have an answer, or after six months otherwise. ## Pull Requests Pull Requests will be considered. Please submit pull requests against the develop branch. Follow the existing code style. Check the tests succeed, including lint. - `npm run test` - `npm run lint` Don't update the CHANGELOG or command version number. That gets done by maintainers when preparing the release. Useful things to include in your request description are: - what problem are you solving? - what Issues does this relate to? - suggested summary for CHANGELOG There are a lot of forms of documentation which could need updating for a change in functionality. It is ok if you want to show us the code to discuss before doing the extra work, and you should say so in your comments so we focus on the concept first before talking about all the other pieces: - TypeScript typings - JSDoc documentation in code - tests - README - examples/ Commander currently has zero production dependencies. That isn't a hard requirement, but is a simple story. Requests which add a dependency are much less likely to be accepted, and we are likely to ask if there alternative approaches to avoid the dependency. - - commander.js-9.0.0/LICENSE000066400000000000000000000021121417504050400151010ustar00rootroot00000000000000(The MIT License) Copyright (c) 2011 TJ Holowaychuk Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. commander.js-9.0.0/Readme.md000066400000000000000000001133501417504050400156220ustar00rootroot00000000000000# Commander.js [![Build Status](https://github.com/tj/commander.js/workflows/build/badge.svg)](https://github.com/tj/commander.js/actions?query=workflow%3A%22build%22) [![NPM Version](http://img.shields.io/npm/v/commander.svg?style=flat)](https://www.npmjs.org/package/commander) [![NPM Downloads](https://img.shields.io/npm/dm/commander.svg?style=flat)](https://npmcharts.com/compare/commander?minimal=true) [![Install Size](https://packagephobia.now.sh/badge?p=commander)](https://packagephobia.now.sh/result?p=commander) The complete solution for [node.js](http://nodejs.org) command-line interfaces. Read this in other languages: English | [简体中文](./Readme_zh-CN.md) - [Commander.js](#commanderjs) - [Installation](#installation) - [Quick Start](#quick-start) - [Declaring _program_ variable](#declaring-program-variable) - [Options](#options) - [Common option types, boolean and value](#common-option-types-boolean-and-value) - [Default option value](#default-option-value) - [Other option types, negatable boolean and boolean|value](#other-option-types-negatable-boolean-and-booleanvalue) - [Required option](#required-option) - [Variadic option](#variadic-option) - [Version option](#version-option) - [More configuration](#more-configuration) - [Custom option processing](#custom-option-processing) - [Commands](#commands) - [Command-arguments](#command-arguments) - [More configuration](#more-configuration-1) - [Custom argument processing](#custom-argument-processing) - [Action handler](#action-handler) - [Stand-alone executable (sub)commands](#stand-alone-executable-subcommands) - [Life cycle hooks](#life-cycle-hooks) - [Automated help](#automated-help) - [Custom help](#custom-help) - [Display help after errors](#display-help-after-errors) - [Display help from code](#display-help-from-code) - [.name](#name) - [.usage](#usage) - [.helpOption(flags, description)](#helpoptionflags-description) - [.addHelpCommand()](#addhelpcommand) - [More configuration](#more-configuration-2) - [Custom event listeners](#custom-event-listeners) - [Bits and pieces](#bits-and-pieces) - [.parse() and .parseAsync()](#parse-and-parseasync) - [Parsing Configuration](#parsing-configuration) - [Legacy options as properties](#legacy-options-as-properties) - [TypeScript](#typescript) - [createCommand()](#createcommand) - [Node options such as `--harmony`](#node-options-such-as---harmony) - [Debugging stand-alone executable subcommands](#debugging-stand-alone-executable-subcommands) - [Display error](#display-error) - [Override exit and output handling](#override-exit-and-output-handling) - [Additional documentation](#additional-documentation) - [Support](#support) - [Commander for enterprise](#commander-for-enterprise) For information about terms used in this document see: [terminology](./docs/terminology.md) ## Installation ```bash 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](./examples/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)); ``` ```sh $ 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](./examples/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(); ``` ```sh $ 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](https://github.com/tj/commander.js/tree/master/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. Multiple short flags may optionally be combined in a single argument following the dash: boolean flags, followed by a single option taking a value (possibly followed by the value). For example `-a -b -p 80` may be written as `-ab -p80` or even `-abp80`. 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 ### Common option types, boolean and value 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](./examples/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}`); ``` ```bash $ 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 ``` `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`. ### Default option value You can specify a default value for an option. Example file: [options-defaults.js](./examples/options-defaults.js) ```js program .option('-c, --cheese ', 'add the specified type of cheese', 'blue'); program.parse(); console.log(`cheese: ${program.opts().cheese}`); ``` ```bash $ pizza-options cheese: blue $ pizza-options --cheese stilton cheese: stilton ``` ### Other option types, negatable boolean and boolean|value 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](./examples/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}`); ``` ```bash $ 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](./examples/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}`); ``` ```bash $ pizza-options no cheese $ pizza-options --cheese add cheese $ pizza-options --cheese mozzarella add cheese type mozzarella ``` For information about possible ambiguous cases, see [options taking varying arguments](./docs/options-taking-varying-arguments.md). ### Required option 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](./examples/options-required.js) ```js program .requiredOption('-c, --cheese ', 'pizza must have cheese'); program.parse(); ``` ```bash $ pizza error: required option '-c, --cheese ' not specified ``` ### Variadic option 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](./examples/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); ``` ```bash $ 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](./docs/options-taking-varying-arguments.md). ### Version option 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'); ``` ```bash $ ./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'); ``` ### More configuration 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](./examples/options-extra.js), [options-env.js](./examples/options-env.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)); ``` ```bash $ 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) -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 Options: { timeout: 60, donate: 20, port: '80' } ``` ### Custom option processing 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](./examples/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); ``` ```bash $ 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](./examples/nestedCommands.js)). 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](./examples/defaultCommand.js)). ### Command-arguments 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](./examples/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](./examples/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](./examples/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}`); }) ; ``` ### Action handler 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](./examples/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](./examples/action-this.js) ```js program .command('serve') .argument('