Update yargs to the latest version 馃殌 #349
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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
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.
Version 7.0.1 of yargs just got published.
The version 7.0.1 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.
Commits
The new version differs by 25 commits .
4df3a10chore(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)49a93fcfix: use path.resolve() to support node 0.10 (#797)3280dd0feat: allow provided config object to extend other configs (#779)e0fbbe5fix: pull in yargs-parser with modified env precedence (#787)0997288fix: context should override parsed argv (#786)There are 25 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 馃尨