yargs-parser v18.1.0

Features

• introduce single-digit boolean aliases (#255) (9c60265)

yargs-parser v18.0.0

⚠ BREAKING CHANGES

• the narg count is now enforced when parsing arrays.

Features

• NaN can now be provided as a value for nargs, indicating "at least" one value is expected for array (#251) (9db4be8)

yargs-parser v17.1.0

Features

• introduce greedy-arrays config, for specifying whether arrays consume multiple positionals (#249) (60e880a)

yargs-parser v17.0.1

Bug Fixes

• normalized keys were not enumerable (#247) (57119f9)

yargs-parser v17.0.0

⚠ BREAKING CHANGES

• this reverts parsing behavior of booleans to that of yargs@14
• objects used during parsing are now created with a null
  prototype. There may be some scenarios where this change in behavior
  leaks externally.

Features

• boolean arguments will not be collected into an implicit array (#236) (34c4e19)
• introduce nargs-eats-options config option (#246) (d50822a)

Bug Fixes

• address bugs with "uknown-options-as-args" (bc023e3)
• array should take precedence over nargs, but enforce nargs (#243) (4cbc188)
• support keys that collide with object prototypes (#234) (1587b6d)
• unknown options terminated with digits now handled by unknown-options-as-args (#238) (d36cdfa)

yargs-parser v16.1.0

⚠ BREAKING CHANGES

• populate error if incompatible narg/count or array/count options are used (#191)

Features

• options that have had their default value used are now tracked (#211) (a525234)
• populate error if incompatible narg/count or array/count options are used (#191) (84a401f)

Reverts

• revert 16.0.0 CHANGELOG entry (920320a)

v13.1.1

Bug Fixes

• convert values to strings when tokenizing (#167) (57b7883)
• nargs should allow duplicates when duplicate-arguments-array=false (#164) (47ccb0b)
• should populate "_" when given config with "short-option-groups" false (#179) (6055974)

v4.0.2

Bug Fixes

• whoops, let's make the assign not change the Object key order (29d069a)

v4.0.1

Bug Fixes

• lodash.assign was deprecated (#59) (5e7eb11)

v4.0.0

Bug Fixes

• coerce should be applied to the final objects and arrays created (#57) (4ca69da)

BREAKING CHANGES

• coerce is no longer applied to individual arguments in an implicit array.