[Snyk] Upgrade commander from 5.0.0 to 5.1.0 #22
Closed
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 5.0.0 to 5.1.0.
✨What is Merge Advice?
We check thousands of dependency upgrade pull requests and CI tests every day to see which upgrades were successfully merged. After crunching this data, we give a recommendation on how safe we think the change is for you to merge without causing issues. Learn more, and share your feedback to help improve this feature. 🙏ℹ️ 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
Added
addCommand()
forhidden
andisDefault
(#1232)Fixed
helpOption
(#1248)Changed
arguments
to improve auto-generated help in editors (#1235).command()
configurationnoHelp
tohidden
(but not remove old support) (#1232)Added
.addCommand()
for adding a separately configured command (#764 #1149).addHelpCommand()
(#1149)-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 usesprocess.argv
if arguments not specified (#1172).parse()
arguments "from", if not following node conventions (#512 #1172)commands
property ofCommand
(#1184)program
property (#1195)createCommand
factory method to simplify subclassing (#1191)Fixed
command:*
for executable subcommands (#809 #1149)Changed
.args
contains command arguments with just recognised options removed (#1032 #1138).option()
(#1119).allowUnknownOption()
(#802 #1138).args
-ab
or--foo=bar
) (#1145).parseOptions()
(#1138)args
in returned result renamedoperands
and does not include anything after first unknown optionunknown
in returned result has arguments after first unknown option including operands, not just options and values.on('command:*', callback)
and other command events passed (changed) results from.parseOptions
, i.e. operands and unknown (#1138)this
rather thanCommand
(#1180).parseAsync
returnsPromise<this>
to be consistent with.parse()
(#1180)Removed
@types/node
(#1146)normalize
(the functionality has been integrated intoparseOptions
) (#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 toisDefault:true
with a named command.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