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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
yargs just published its new version 7.0.1.
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 :sparkles:
You rock!
:palm_tree:
The new version differs by 79 commits .
4df3a10
chore(release): 7.0.1
9c03fa4
fix: --help with default command should print top-level help (#810)
5334370
docs: env vars now take precedence over config file/objects (#808)
bc56468
docs: a couple small twaks to the CHANGELOG
57dc7b5
chore(release): 7.0.0
f3f074b
fix: positional arguments of sub-commands threw strict() exception (#805)
a607061
fix: console.warn() rather than throwing errors when api signatures are incorrect (#804)
d78a0f5
feat: introduces support for default commands, using the '*' identifier (#785)
8a992f5
fix: errors were not bubbling appropriately from sub-commands to top-level (#802)
07e39b7
fix: running parse() multiple times on the same yargs instance caused exception if help() enabled (#790)
48575cd
fix: context variables are now recognized in strict() mode (#796)
49a93fc
fix: use path.resolve() to support node 0.10 (#797)
3280dd0
feat: allow provided config object to extend other configs (#779)
e0fbbe5
fix: pull in yargs-parser with modified env precedence (#787)
0997288
fix: context should override parsed argv (#786)
There are 79 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.