Update yargs to version 7.0.2 🚀 #1431
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #1431 +/- ##
=======================================
Coverage 99.74% 99.74%
=======================================
Files 141 141
Lines 2354 2354
=======================================
Hits 2348 2348
Misses 6 6Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello lovely humans,
yargs just published its new version 7.0.2.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of yargs.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 29 commits .
8756a3cchore(release): 7.0.2fa86602chore: fix test messageb3eb2fefix: populating placeholder arguments broke validation82c7a4euse console.log instead of util.print, fix #8134df3a10chore(release): 7.0.19c03fa4fix: --help with default command should print top-level help (#810)5334370docs: env vars now take precedence over config file/objects (#808)bc56468docs: a couple small twaks to the CHANGELOG57dc7b5chore(release): 7.0.0f3f074bfix: positional arguments of sub-commands threw strict() exception (#805)a607061fix: console.warn() rather than throwing errors when api signatures are incorrect (#804)d78a0f5feat: introduces support for default commands, using the '*' identifier (#785)8a992f5fix: errors were not bubbling appropriately from sub-commands to top-level (#802)07e39b7fix: running parse() multiple times on the same yargs instance caused exception if help() enabled (#790)48575cdfix: context variables are now recognized in strict() mode (#796)There are 29 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.