Update gh-pages 6.2.0 → 6.3.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ gh-pages (6.2.0 → 6.3.0) · Repo · Changelog

Release Notes

6.3.0

What's Changed

• Bump chai from 4.3.10 to 4.5.0 by @dependabot in #584
• Bump mocha from 10.7.3 to 10.8.2 by @dependabot in #583
• Bump mocha from 10.8.2 to 11.0.1 by @dependabot in #590
• Bump eslint-config-tschaub from 14.1.2 to 15.1.0 by @dependabot in #587
• Bump commander from 11.1.0 to 13.0.0 by @dependabot in #591
• Support filenames starting with - by @sherlockdoyle in #593

New Contributors

• @sherlockdoyle made their first contribution in #593

Full Changelog: v6.2.0...v6.3.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 16 commits:

• 6.3.0
• Log changes
• Merge pull request #593 from sherlockdoyle/fix-592
• fixes #592
• Merge pull request #591 from tschaub/dependabot/npm_and_yarn/commander-13.0.0
• Remove extra argument
• Bump commander from 11.1.0 to 13.0.0
• Merge pull request #587 from tschaub/dependabot/npm_and_yarn/eslint-config-tschaub-15.1.0
• Updates to work with ESLint 9
• Bump eslint-config-tschaub from 14.1.2 to 15.1.0
• Merge pull request #590 from tschaub/dependabot/npm_and_yarn/mocha-11.0.1
• Bump mocha from 10.8.2 to 11.0.1
• Merge pull request #583 from tschaub/dependabot/npm_and_yarn/mocha-10.8.2
• Merge pull request #584 from tschaub/dependabot/npm_and_yarn/chai-4.5.0
• Bump chai from 4.3.10 to 4.5.0
• Bump mocha from 10.7.3 to 10.8.2

↗️ commander (indirect, 11.1.0 → 13.0.0) · Repo · Changelog

Release Notes

13.0.0

Added

• support multiple calls to .parse() with default settings (#2299)
• add .saveStateBeforeParse() and .restoreStateBeforeParse() for use by subclasses (#2299)
• style routines like styleTitle() to add color to help using .configureHelp() or Help subclass (#2251)
• color related support in .configureOutput() for getOutHasColors(), getErrHasColors(), and stripColor() (#2251)
• Help property for minWidthToWrap (#2251)
• Help methods for displayWidth(), boxWrap(), preformatted() et al (#2251)

Changed

• Breaking: excess command-arguments cause an error by default, see migration tips (#2223)
• Breaking: throw during Option construction for unsupported option flags, like multiple characters after single - (#2270)
• Breaking: throw on multiple calls to .parse() if storeOptionsAsProperties: true (#2299)
• TypeScript: include implicit this in parameters for action handler callback (#2197)

Deleted

• Breaking: Help.wrap() refactored into formatItem() and boxWrap() (#2251)

Migration Tips

Excess command-arguments

It is now an error for the user to specify more command-arguments than are expected. (allowExcessArguments is now false by default.)

Old code:

program.option('-p, --port <number>', 'port number');
program.action((options) => {
  console.log(program.args);
});

Now shows an error:

$ node example.js a b c
error: too many arguments. Expected 0 arguments but got 3.

You can declare the expected arguments. The help will then be more accurate too. Note that declaring
new arguments will change what is passed to the action handler.

program.option('-p, --port <number>', 'port number');
program.argument('[args...]', 'remote command and arguments'); // expecting zero or more arguments
program.action((args, options) => {
  console.log(args);
});

Or you could suppress the error, useful for minimising changes in legacy code.

program.option('-p, --port', 'port number');
program.allowExcessArguments();
program.action((options) => {
  console.log(program.args);
});

12.1.0

Added

• auto-detect special node flags node --eval and node --print when call .parse() with no arguments (#2164)

Changed

• prefix require of Node.js core modules with node: (#2170)
• format source files with Prettier (#2180)
• switch from StandardJS to directly calling ESLint for linting (#2153)
• extend security support for previous major version of Commander (#2150)

Removed

• removed unimplemented Option.fullDescription from TypeScript definition (#2191)

12.0.0

Added

• .addHelpOption() as another way of configuring built-in help option (#2006)
• .helpCommand() for configuring built-in help command (#2087)

Fixed

• Breaking: use non-zero exit code when spawned executable subcommand terminates due to a signal (#2023)
• Breaking: check passThroughOptions constraints when using .addCommand and throw if parent command does not have .enablePositionalOptions() enabled (#1937)

Changed

• Breaking: Commander 12 requires Node.js v18 or higher (#2027)
• Breaking: throw an error if add an option with a flag which is already in use (#2055)
• Breaking: throw an error if add a command with name or alias which is already in use (#2059)
• Breaking: throw error when calling .storeOptionsAsProperties() after setting an option value (#1928)
• replace non-standard JSDoc of @api private with documented @private (#1949)
• .addHelpCommand() now takes a Command (passing string or boolean still works as before but deprecated) (#2087)
• refactor internal implementation of built-in help option (#2006)
• refactor internal implementation of built-in help command (#2087)

Deprecated

• .addHelpCommand() passing string or boolean (use .helpCommand() or pass a Command) (#2087)

Removed

• Breaking: removed default export of a global Command instance from CommonJS (use the named program export instead) (#2017)

Migration Tips

global program

If you are using the deprecated default import of the global Command object, you need to switch to using a named import (or create a new Command).

// const program = require('commander');
const { program } = require('commander');

option and command clashes

A couple of configuration problems now throw an error, which will pick up issues in existing programs:

• adding an option which uses the same flag as a previous option
• adding a command which uses the same name or alias as a previous command

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)