yargs v14.0.0 Release Notes
Release Date: 2019-07-30 // over 4 years ago-
โ 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