v9.0.0 pre-release available

[shadowspawn]

Highlights

• simplified ECMAScript import
• added Option.preset()
• changes to boolean options and optional options used with default value
• reworked search for subcommand stand-alone executables
• added .error()
• added .optsWithGlobals().

Release Notes:

• https://github.com/tj/commander.js/releases/tag/v9.0.0-0
• https://github.com/tj/commander.js/releases/tag/v9.0.0-1

README: https://github.com/tj/commander.js/blob/release/9.x/Readme.md

You can try the prerelease with:

npm install commander@next

Open an issue or add a comment here for any problems you encounter.

[kuncevic]

Any braking changes planned for v9? (except using Node.js v12.20.0 or higher)

[shadowspawn]

Check the Release Notes. The potentially breaking changes have Breaking on the front. In particular:

• Breaking: default value specified for boolean option now always used as default value (see .preset() to match some previous behaviours) (Rework option defaults and add preset #1652)
• 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) (Rework default program name, and searching for subcommands #1571)

A behaviour change some people might notice is a bug fix rather than a breaking change as such:

• 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 (Rework option defaults and add preset #1652)

[shadowspawn]

And no further breaking changes planned.

[shadowspawn]

v9.0.0-1 published with .error() and .optsWithGlobals().

https://github.com/tj/commander.js/releases/tag/v9.0.0-1

[shadowspawn]

I'll update branch tomorrow for release by you this weekend, if suits @abetomo ?

[abetomo]

Thanks for the update. Let's release it this weekend!

[shadowspawn]

Commander v9 has been released.