refactor: upgrade commander from 9.0.0 to 9.1.0 #2089
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade commander from 9.0.0 to 9.1.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: commander
-
9.1.0 - 2022-03-18
- Option
- (developer) CodeQL configuration for GitHub Actions (#1698)
-
9.0.0 - 2022-01-29
- simpler ECMAScript import (#1589)
- Option.preset() allows specifying value/arg for option when used without option-argument (especially optional, but also boolean option) (#1652)
- throw with helpful message if pass
- .
- Breaking: Commander 9 requires Node.js v12.20.0 or higher
- update package-lock.json to lockfile@2 format (#1659)
- 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
- removed restriction that nested subcommands must specify
- TypeScript: allow passing readonly string array to
- TypeScript: allow passing readonly string array to
- 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)
- Breaking: removed internal fallback to
from commander GitHub release notesAdded
.conflicts()to set conflicting options which can not be specified together (#1678)Added
.executableDir()for custom search for subcommands (#1571)Optionto.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
showSuggestionAfterErroris now on by default (#1657)executableFile(#1571)executableFile(#1571).choices()(#1667).parse(),.parseAsync(),.aliases()(#1669)Fixed
Removed
require.main.filenamewhen script not known from arguments passed to.parse()(can supply details using
.name(), and.executableDir()orexecutableFile) (#1571)Commit messages
Package name: commander
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs