Update yargs to the latest version 🚀

[greenkeeper]

Version 7.0.1 of yargs just got published.

Dependency	yargs
Current Version	6.6.0
Type	devDependency

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 .

• 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 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 🌴

[coveralls]

Coverage remained the same at 100.0% when pulling 509fd81 on greenkeeper/yargs-7.0.1 into 5563699 on master.

[AppVeyorBot]

✅ Build winston-aws-cloudwatch 235 completed (commit 23552c3d57 by @Greenkeeper[bot])

[greenkeeper]

Version 7.0.2 just got published.

Update to this version instead 🚀

Commits

The new version differs by 4 commits .

• 8756a3c chore(release): 7.0.2
• fa86602 chore: fix test message
• b3eb2fe fix: populating placeholder arguments broke validation
• 82c7a4e use console.log instead of util.print, fix #813

See the full diff.

[greenkeeper]

Version 7.1.0 just got published.

Update to this version instead 🚀

Commits

The new version differs by 8 commits .

• e7359d6 chore(release): 7.1.0
• c357412 docs: switch to conventional commits badge [ci skip] (#850)
• 17e89bd fix: we shouldn't output help if we've printed a prior help-like message (#847)
• 50c9acd chore: add editorconfig (#848)
• 360e301 fix: get terminalWidth in non interactive mode no longer causes a validation exception (#837)
• fde0564 feat: add support for numeric commands (#825)
• c748dd2 fix: fix demandOption no longer treats 'false' as truthy (#829)
• e0b4efb test: Made unit test passing with node-chakracore

See the full diff.