Upgrade yargs to version 14.0.0

[depfu[bot]]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ yargs (^13.1.0 → ^14.0.0) · Repo · Changelog

Release Notes

14.0.0 (from changelog)

⚠ BREAKING CHANGES

• we now only officially support yargs.$0 parameter and discourage direct access to yargs.parsed
• previously to this fix methods like yargs.getOptions() contained the state of the last command to execute.
• do not allow additional positionals in strict mode

Bug Fixes

• calling parse multiple times now appropriately maintains state (#1137) (#1369) (026b151)
• prefer user supplied script name in usage (#1383) (28c74b9)
• deps: use decamelize from npm instead of vendored copy (#1377) (015eeb9)
• examples: fix usage-options.js to reflect current API (#1375) (6e5b76b)
• do not allow additional positionals in strict mode (35d777c)
• properties accessed on singleton now reflect current state of instance (#1366) (409d35b)
• tolerate null prototype for config objects with extends (#1376) (3d26d11), closes #1372
• yargs.parsed now populated before returning, when yargs.parse() called with no args (#1382) (e3981fd), closes #1382

Features

• adds support for multiple epilog messages (#1384) (07a5554)
• allow completionCommand to be set via showCompletionScript (#1385) (5562853)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 15 commits:

• chore(release): 14.0.0
• chore: upgrade standard-version
• docs: add TypeScript documentation (#1381)
• feat: allow completionCommand to be set via showCompletionScript (#1385)
• feat: adds support for multiple epilog messages (#1384)
• fix: prefer user supplied script name in usage (#1383)
• fix! yargs.parsed now populated before returning, when yargs.parse() called with no args (#1382)
• fix!: calling parse multiple times now appropriately maintains state (#1137) (#1369)
• fix(examples): fix usage-options.js to reflect current API (#1375)
• fix: tolerate null prototype for config objects with `extends` (#1376)
• fix(deps): use decamelize from npm instead of vendored copy (#1377)
• fix: properties accessed on singleton now reflect current state of instance (#1366)
• docs: add section on dashes in string arguments (#1371)
• docs: fix emphasis of note to .parserConfiguration (#1361)
• fix!: do not allow additional positionals in strict mode

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[coveralls]

Coverage remained the same at 82.941% when pulling 4887a5d3d30e0175dc9a2ba6674ba284c68e9de6 on depfu/update/npm/yargs-14.0.0 into 694c07b9e726d53adcb25099a2a2083b51424a6a on master.