1 | # Changelog
|
2 |
|
3 | All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
|
4 |
|
5 | ### [18.1.1](https://www.github.com/yargs/yargs-parser/compare/v18.1.0...v18.1.1) (2020-03-16)
|
6 |
|
7 |
|
8 | ### Bug Fixes
|
9 |
|
10 | * \_\_proto\_\_ will now be replaced with \_\_\_proto\_\_\_ in parse ([#258](https://www.github.com/yargs/yargs-parser/issues/258)), patching a potential
|
11 | prototype pollution vulnerability. This was reported by the Snyk Security Research Team.([63810ca](https://www.github.com/yargs/yargs-parser/commit/63810ca1ae1a24b08293a4d971e70e058c7a41e2))
|
12 |
|
13 | ## [18.1.0](https://www.github.com/yargs/yargs-parser/compare/v18.0.0...v18.1.0) (2020-03-07)
|
14 |
|
15 |
|
16 | ### Features
|
17 |
|
18 | * introduce single-digit boolean aliases ([#255](https://www.github.com/yargs/yargs-parser/issues/255)) ([9c60265](https://www.github.com/yargs/yargs-parser/commit/9c60265fd7a03cb98e6df3e32c8c5e7508d9f56f))
|
19 |
|
20 | ## [18.0.0](https://www.github.com/yargs/yargs-parser/compare/v17.1.0...v18.0.0) (2020-03-02)
|
21 |
|
22 |
|
23 | ### ⚠ BREAKING CHANGES
|
24 |
|
25 | * the narg count is now enforced when parsing arrays.
|
26 |
|
27 | ### Features
|
28 |
|
29 | * NaN can now be provided as a value for nargs, indicating "at least" one value is expected for array ([#251](https://www.github.com/yargs/yargs-parser/issues/251)) ([9db4be8](https://www.github.com/yargs/yargs-parser/commit/9db4be81417a2c7097128db34d86fe70ef4af70c))
|
30 |
|
31 | ## [17.1.0](https://www.github.com/yargs/yargs-parser/compare/v17.0.1...v17.1.0) (2020-03-01)
|
32 |
|
33 |
|
34 | ### Features
|
35 |
|
36 | * introduce greedy-arrays config, for specifying whether arrays consume multiple positionals ([#249](https://www.github.com/yargs/yargs-parser/issues/249)) ([60e880a](https://www.github.com/yargs/yargs-parser/commit/60e880a837046314d89fa4725f923837fd33a9eb))
|
37 |
|
38 | ### [17.0.1](https://www.github.com/yargs/yargs-parser/compare/v17.0.0...v17.0.1) (2020-02-29)
|
39 |
|
40 |
|
41 | ### Bug Fixes
|
42 |
|
43 | * normalized keys were not enumerable ([#247](https://www.github.com/yargs/yargs-parser/issues/247)) ([57119f9](https://www.github.com/yargs/yargs-parser/commit/57119f9f17cf27499bd95e61c2f72d18314f11ba))
|
44 |
|
45 | ## [17.0.0](https://www.github.com/yargs/yargs-parser/compare/v16.1.0...v17.0.0) (2020-02-10)
|
46 |
|
47 |
|
48 | ### ⚠ BREAKING CHANGES
|
49 |
|
50 | * this reverts parsing behavior of booleans to that of yargs@14
|
51 | * objects used during parsing are now created with a null
|
52 | prototype. There may be some scenarios where this change in behavior
|
53 | leaks externally.
|
54 |
|
55 | ### Features
|
56 |
|
57 | * boolean arguments will not be collected into an implicit array ([#236](https://www.github.com/yargs/yargs-parser/issues/236)) ([34c4e19](https://www.github.com/yargs/yargs-parser/commit/34c4e19bae4e7af63e3cb6fa654a97ed476e5eb5))
|
58 | * introduce nargs-eats-options config option ([#246](https://www.github.com/yargs/yargs-parser/issues/246)) ([d50822a](https://www.github.com/yargs/yargs-parser/commit/d50822ac10e1b05f2e9643671ca131ac251b6732))
|
59 |
|
60 |
|
61 | ### Bug Fixes
|
62 |
|
63 | * address bugs with "uknown-options-as-args" ([bc023e3](https://www.github.com/yargs/yargs-parser/commit/bc023e3b13e20a118353f9507d1c999bf388a346))
|
64 | * array should take precedence over nargs, but enforce nargs ([#243](https://www.github.com/yargs/yargs-parser/issues/243)) ([4cbc188](https://www.github.com/yargs/yargs-parser/commit/4cbc188b7abb2249529a19c090338debdad2fe6c))
|
65 | * support keys that collide with object prototypes ([#234](https://www.github.com/yargs/yargs-parser/issues/234)) ([1587b6d](https://www.github.com/yargs/yargs-parser/commit/1587b6d91db853a9109f1be6b209077993fee4de))
|
66 | * unknown options terminated with digits now handled by unknown-options-as-args ([#238](https://www.github.com/yargs/yargs-parser/issues/238)) ([d36cdfa](https://www.github.com/yargs/yargs-parser/commit/d36cdfa854254d7c7e0fe1d583818332ac46c2a5))
|
67 |
|
68 | ## [16.1.0](https://www.github.com/yargs/yargs-parser/compare/v16.0.0...v16.1.0) (2019-11-01)
|
69 |
|
70 |
|
71 | ### ⚠ BREAKING CHANGES
|
72 |
|
73 | * populate error if incompatible narg/count or array/count options are used (#191)
|
74 |
|
75 | ### Features
|
76 |
|
77 | * options that have had their default value used are now tracked ([#211](https://www.github.com/yargs/yargs-parser/issues/211)) ([a525234](https://www.github.com/yargs/yargs-parser/commit/a525234558c847deedd73f8792e0a3b77b26e2c0))
|
78 | * populate error if incompatible narg/count or array/count options are used ([#191](https://www.github.com/yargs/yargs-parser/issues/191)) ([84a401f](https://www.github.com/yargs/yargs-parser/commit/84a401f0fa3095e0a19661670d1570d0c3b9d3c9))
|
79 |
|
80 |
|
81 | ### Reverts
|
82 |
|
83 | * revert 16.0.0 CHANGELOG entry ([920320a](https://www.github.com/yargs/yargs-parser/commit/920320ad9861bbfd58eda39221ae211540fc1daf))
|
84 |
|
85 | ## [15.0.0](https://github.com/yargs/yargs-parser/compare/v14.0.0...v15.0.0) (2019-10-07)
|
86 |
|
87 |
|
88 | ### Features
|
89 |
|
90 | * rework `collect-unknown-options` into `unknown-options-as-args`, providing more comprehensive functionality ([ef771ca](https://github.com/yargs/yargs-parser/commit/ef771ca))
|
91 |
|
92 |
|
93 | ### BREAKING CHANGES
|
94 |
|
95 | * rework `collect-unknown-options` into `unknown-options-as-args`, providing more comprehensive functionality
|
96 |
|
97 |
|
98 |
|
99 | ## [14.0.0](https://github.com/yargs/yargs-parser/compare/v13.1.1...v14.0.0) (2019-09-06)
|
100 |
|
101 |
|
102 | ### Bug Fixes
|
103 |
|
104 | * boolean arrays with default values ([#185](https://github.com/yargs/yargs-parser/issues/185)) ([7d42572](https://github.com/yargs/yargs-parser/commit/7d42572))
|
105 | * boolean now behaves the same as other array types ([#184](https://github.com/yargs/yargs-parser/issues/184)) ([17ca3bd](https://github.com/yargs/yargs-parser/commit/17ca3bd))
|
106 | * eatNargs() for 'opt.narg === 0' and boolean typed options ([#188](https://github.com/yargs/yargs-parser/issues/188)) ([c5a1db0](https://github.com/yargs/yargs-parser/commit/c5a1db0))
|
107 | * maybeCoerceNumber now takes precedence over coerce return value ([#182](https://github.com/yargs/yargs-parser/issues/182)) ([2f26436](https://github.com/yargs/yargs-parser/commit/2f26436))
|
108 | * take into account aliases when appending arrays from config object ([#199](https://github.com/yargs/yargs-parser/issues/199)) ([f8a2d3f](https://github.com/yargs/yargs-parser/commit/f8a2d3f))
|
109 |
|
110 |
|
111 | ### Features
|
112 |
|
113 | * add configuration option to "collect-unknown-options" ([#181](https://github.com/yargs/yargs-parser/issues/181)) ([7909cc4](https://github.com/yargs/yargs-parser/commit/7909cc4))
|
114 | * maybeCoerceNumber() now takes into account arrays ([#187](https://github.com/yargs/yargs-parser/issues/187)) ([31c204b](https://github.com/yargs/yargs-parser/commit/31c204b))
|
115 |
|
116 |
|
117 | ### BREAKING CHANGES
|
118 |
|
119 | * unless "parse-numbers" is set to "false", arrays of numeric strings are now parsed as numbers, rather than strings.
|
120 | * we have dropped the broken "defaulted" functionality; we would like to revisit adding this in the future.
|
121 | * maybeCoerceNumber now takes precedence over coerce return value (#182)
|
122 |
|
123 |
|
124 |
|
125 | ### [13.1.1](https://www.github.com/yargs/yargs-parser/compare/v13.1.0...v13.1.1) (2019-06-10)
|
126 |
|
127 |
|
128 | ### Bug Fixes
|
129 |
|
130 | * convert values to strings when tokenizing ([#167](https://www.github.com/yargs/yargs-parser/issues/167)) ([57b7883](https://www.github.com/yargs/yargs-parser/commit/57b7883))
|
131 | * nargs should allow duplicates when duplicate-arguments-array=false ([#164](https://www.github.com/yargs/yargs-parser/issues/164)) ([47ccb0b](https://www.github.com/yargs/yargs-parser/commit/47ccb0b))
|
132 | * should populate "_" when given config with "short-option-groups" false ([#179](https://www.github.com/yargs/yargs-parser/issues/179)) ([6055974](https://www.github.com/yargs/yargs-parser/commit/6055974))
|
133 |
|
134 | ## [13.1.0](https://github.com/yargs/yargs-parser/compare/v13.0.0...v13.1.0) (2019-05-05)
|
135 |
|
136 |
|
137 | ### Features
|
138 |
|
139 | * add `strip-aliased` and `strip-dashed` configuration options. ([#172](https://github.com/yargs/yargs-parser/issues/172)) ([a3936aa](https://github.com/yargs/yargs-parser/commit/a3936aa))
|
140 | * support boolean which do not consume next argument. ([#171](https://github.com/yargs/yargs-parser/issues/171)) ([0ae7fcb](https://github.com/yargs/yargs-parser/commit/0ae7fcb))
|
141 |
|
142 |
|
143 |
|
144 | <a name="13.0.0"></a>
|
145 | # [13.0.0](https://github.com/yargs/yargs-parser/compare/v12.0.0...v13.0.0) (2019-02-02)
|
146 |
|
147 |
|
148 | ### Features
|
149 |
|
150 | * don't coerce number from string with leading '0' or '+' ([#158](https://github.com/yargs/yargs-parser/issues/158)) ([18d0fd5](https://github.com/yargs/yargs-parser/commit/18d0fd5))
|
151 |
|
152 |
|
153 | ### BREAKING CHANGES
|
154 |
|
155 | * options with leading '+' or '0' now parse as strings
|
156 |
|
157 |
|
158 |
|
159 | <a name="12.0.0"></a>
|
160 | # [12.0.0](https://github.com/yargs/yargs-parser/compare/v11.1.1...v12.0.0) (2019-01-29)
|
161 |
|
162 |
|
163 | ### Bug Fixes
|
164 |
|
165 | * better handling of quoted strings ([#153](https://github.com/yargs/yargs-parser/issues/153)) ([2fb71b2](https://github.com/yargs/yargs-parser/commit/2fb71b2))
|
166 |
|
167 |
|
168 | ### Features
|
169 |
|
170 | * default value is now used if no right-hand value provided for numbers/strings ([#156](https://github.com/yargs/yargs-parser/issues/156)) ([5a7c46a](https://github.com/yargs/yargs-parser/commit/5a7c46a))
|
171 |
|
172 |
|
173 | ### BREAKING CHANGES
|
174 |
|
175 | * a flag with no right-hand value no longer populates defaulted options with `undefined`.
|
176 | * quotes at beginning and endings of strings are not removed during parsing.
|
177 |
|
178 |
|
179 |
|
180 | <a name="11.1.1"></a>
|
181 | ## [11.1.1](https://github.com/yargs/yargs-parser/compare/v11.1.0...v11.1.1) (2018-11-19)
|
182 |
|
183 |
|
184 | ### Bug Fixes
|
185 |
|
186 | * ensure empty string is added into argv._ ([#140](https://github.com/yargs/yargs-parser/issues/140)) ([79cda98](https://github.com/yargs/yargs-parser/commit/79cda98))
|
187 |
|
188 |
|
189 | ### Reverts
|
190 |
|
191 | * make requiresArg work in conjunction with arrays ([#136](https://github.com/yargs/yargs-parser/issues/136)) ([f4a3063](https://github.com/yargs/yargs-parser/commit/f4a3063))
|
192 |
|
193 |
|
194 |
|
195 | <a name="11.1.0"></a>
|
196 | # [11.1.0](https://github.com/yargs/yargs-parser/compare/v11.0.0...v11.1.0) (2018-11-10)
|
197 |
|
198 |
|
199 | ### Bug Fixes
|
200 |
|
201 | * handling of one char alias ([#139](https://github.com/yargs/yargs-parser/issues/139)) ([ee56e31](https://github.com/yargs/yargs-parser/commit/ee56e31))
|
202 |
|
203 |
|
204 | ### Features
|
205 |
|
206 | * add halt-at-non-option configuration option ([#130](https://github.com/yargs/yargs-parser/issues/130)) ([a849fce](https://github.com/yargs/yargs-parser/commit/a849fce))
|
207 |
|
208 |
|
209 |
|
210 | <a name="11.0.0"></a>
|
211 | # [11.0.0](https://github.com/yargs/yargs-parser/compare/v10.1.0...v11.0.0) (2018-10-06)
|
212 |
|
213 |
|
214 | ### Bug Fixes
|
215 |
|
216 | * flatten-duplicate-arrays:false for more than 2 arrays ([#128](https://github.com/yargs/yargs-parser/issues/128)) ([2bc395f](https://github.com/yargs/yargs-parser/commit/2bc395f))
|
217 | * hyphenated flags combined with dot notation broke parsing ([#131](https://github.com/yargs/yargs-parser/issues/131)) ([dc788da](https://github.com/yargs/yargs-parser/commit/dc788da))
|
218 | * make requiresArg work in conjunction with arrays ([#136](https://github.com/yargs/yargs-parser/issues/136)) ([77ae1d4](https://github.com/yargs/yargs-parser/commit/77ae1d4))
|
219 |
|
220 |
|
221 | ### Chores
|
222 |
|
223 | * update dependencies ([6dc42a1](https://github.com/yargs/yargs-parser/commit/6dc42a1))
|
224 |
|
225 |
|
226 | ### Features
|
227 |
|
228 | * also add camelCase array options ([#125](https://github.com/yargs/yargs-parser/issues/125)) ([08c0117](https://github.com/yargs/yargs-parser/commit/08c0117))
|
229 | * array.type can now be provided, supporting coercion ([#132](https://github.com/yargs/yargs-parser/issues/132)) ([4b8cfce](https://github.com/yargs/yargs-parser/commit/4b8cfce))
|
230 |
|
231 |
|
232 | ### BREAKING CHANGES
|
233 |
|
234 | * drops Node 4 support
|
235 | * the argv object is now populated differently (correctly) when hyphens and dot notation are used in conjunction.
|
236 |
|
237 |
|
238 |
|
239 | <a name="10.1.0"></a>
|
240 | # [10.1.0](https://github.com/yargs/yargs-parser/compare/v10.0.0...v10.1.0) (2018-06-29)
|
241 |
|
242 |
|
243 | ### Features
|
244 |
|
245 | * add `set-placeholder-key` configuration ([#123](https://github.com/yargs/yargs-parser/issues/123)) ([19386ee](https://github.com/yargs/yargs-parser/commit/19386ee))
|
246 |
|
247 |
|
248 |
|
249 | <a name="10.0.0"></a>
|
250 | # [10.0.0](https://github.com/yargs/yargs-parser/compare/v9.0.2...v10.0.0) (2018-04-04)
|
251 |
|
252 |
|
253 | ### Bug Fixes
|
254 |
|
255 | * do not set boolean flags if not defined in `argv` ([#119](https://github.com/yargs/yargs-parser/issues/119)) ([f6e6599](https://github.com/yargs/yargs-parser/commit/f6e6599))
|
256 |
|
257 |
|
258 | ### BREAKING CHANGES
|
259 |
|
260 | * `boolean` flags defined without a `default` value will now behave like other option type and won't be set in the parsed results when the user doesn't set the corresponding CLI arg.
|
261 |
|
262 | Previous behavior:
|
263 | ```js
|
264 | var parse = require('yargs-parser');
|
265 |
|
266 | parse('--flag', {boolean: ['flag']});
|
267 | // => { _: [], flag: true }
|
268 |
|
269 | parse('--no-flag', {boolean: ['flag']});
|
270 | // => { _: [], flag: false }
|
271 |
|
272 | parse('', {boolean: ['flag']});
|
273 | // => { _: [], flag: false }
|
274 | ```
|
275 |
|
276 | New behavior:
|
277 | ```js
|
278 | var parse = require('yargs-parser');
|
279 |
|
280 | parse('--flag', {boolean: ['flag']});
|
281 | // => { _: [], flag: true }
|
282 |
|
283 | parse('--no-flag', {boolean: ['flag']});
|
284 | // => { _: [], flag: false }
|
285 |
|
286 | parse('', {boolean: ['flag']});
|
287 | // => { _: [] } => flag not set similarly to other option type
|
288 | ```
|
289 |
|
290 |
|
291 |
|
292 | <a name="9.0.2"></a>
|
293 | ## [9.0.2](https://github.com/yargs/yargs-parser/compare/v9.0.1...v9.0.2) (2018-01-20)
|
294 |
|
295 |
|
296 | ### Bug Fixes
|
297 |
|
298 | * nargs was still aggressively consuming too many arguments ([9b28aad](https://github.com/yargs/yargs-parser/commit/9b28aad))
|
299 |
|
300 |
|
301 |
|
302 | <a name="9.0.1"></a>
|
303 | ## [9.0.1](https://github.com/yargs/yargs-parser/compare/v9.0.0...v9.0.1) (2018-01-20)
|
304 |
|
305 |
|
306 | ### Bug Fixes
|
307 |
|
308 | * nargs was consuming too many arguments ([4fef206](https://github.com/yargs/yargs-parser/commit/4fef206))
|
309 |
|
310 |
|
311 |
|
312 | <a name="9.0.0"></a>
|
313 | # [9.0.0](https://github.com/yargs/yargs-parser/compare/v8.1.0...v9.0.0) (2018-01-20)
|
314 |
|
315 |
|
316 | ### Features
|
317 |
|
318 | * narg arguments no longer consume flag arguments ([#114](https://github.com/yargs/yargs-parser/issues/114)) ([60bb9b3](https://github.com/yargs/yargs-parser/commit/60bb9b3))
|
319 |
|
320 |
|
321 | ### BREAKING CHANGES
|
322 |
|
323 | * arguments of form --foo, -abc, will no longer be consumed by nargs
|
324 |
|
325 |
|
326 |
|
327 | <a name="8.1.0"></a>
|
328 | # [8.1.0](https://github.com/yargs/yargs-parser/compare/v8.0.0...v8.1.0) (2017-12-20)
|
329 |
|
330 |
|
331 | ### Bug Fixes
|
332 |
|
333 | * allow null config values ([#108](https://github.com/yargs/yargs-parser/issues/108)) ([d8b14f9](https://github.com/yargs/yargs-parser/commit/d8b14f9))
|
334 | * ensure consistent parsing of dot-notation arguments ([#102](https://github.com/yargs/yargs-parser/issues/102)) ([c9bd79c](https://github.com/yargs/yargs-parser/commit/c9bd79c))
|
335 | * implement [@antoniom](https://github.com/antoniom)'s fix for camel-case expansion ([3087e1d](https://github.com/yargs/yargs-parser/commit/3087e1d))
|
336 | * only run coercion functions once, despite aliases. ([#76](https://github.com/yargs/yargs-parser/issues/76)) ([#103](https://github.com/yargs/yargs-parser/issues/103)) ([507aaef](https://github.com/yargs/yargs-parser/commit/507aaef))
|
337 | * scientific notation circumvented bounds check ([#110](https://github.com/yargs/yargs-parser/issues/110)) ([3571f57](https://github.com/yargs/yargs-parser/commit/3571f57))
|
338 | * tokenizer should ignore spaces at the beginning of the argString ([#106](https://github.com/yargs/yargs-parser/issues/106)) ([f34ead9](https://github.com/yargs/yargs-parser/commit/f34ead9))
|
339 |
|
340 |
|
341 | ### Features
|
342 |
|
343 | * make combining arrays a configurable option ([#111](https://github.com/yargs/yargs-parser/issues/111)) ([c8bf536](https://github.com/yargs/yargs-parser/commit/c8bf536))
|
344 | * merge array from arguments with array from config ([#83](https://github.com/yargs/yargs-parser/issues/83)) ([806ddd6](https://github.com/yargs/yargs-parser/commit/806ddd6))
|
345 |
|
346 |
|
347 |
|
348 | <a name="8.0.0"></a>
|
349 | # [8.0.0](https://github.com/yargs/yargs-parser/compare/v7.0.0...v8.0.0) (2017-10-05)
|
350 |
|
351 |
|
352 | ### Bug Fixes
|
353 |
|
354 | * Ignore multiple spaces between arguments. ([#100](https://github.com/yargs/yargs-parser/issues/100)) ([d137227](https://github.com/yargs/yargs-parser/commit/d137227))
|
355 |
|
356 |
|
357 | ### Features
|
358 |
|
359 | * allow configuration of prefix for boolean negation ([#94](https://github.com/yargs/yargs-parser/issues/94)) ([00bde7d](https://github.com/yargs/yargs-parser/commit/00bde7d))
|
360 | * reworking how numbers are parsed ([#104](https://github.com/yargs/yargs-parser/issues/104)) ([fba00eb](https://github.com/yargs/yargs-parser/commit/fba00eb))
|
361 |
|
362 |
|
363 | ### BREAKING CHANGES
|
364 |
|
365 | * strings that fail `Number.isSafeInteger()` are no longer coerced into numbers.
|
366 |
|
367 |
|
368 |
|
369 | <a name="7.0.0"></a>
|
370 | # [7.0.0](https://github.com/yargs/yargs-parser/compare/v6.0.1...v7.0.0) (2017-05-02)
|
371 |
|
372 |
|
373 | ### Chores
|
374 |
|
375 | * revert populate-- logic ([#91](https://github.com/yargs/yargs-parser/issues/91)) ([6003e6d](https://github.com/yargs/yargs-parser/commit/6003e6d))
|
376 |
|
377 |
|
378 | ### BREAKING CHANGES
|
379 |
|
380 | * populate-- now defaults to false.
|
381 |
|
382 |
|
383 |
|
384 | <a name="6.0.1"></a>
|
385 | ## [6.0.1](https://github.com/yargs/yargs-parser/compare/v6.0.0...v6.0.1) (2017-05-01)
|
386 |
|
387 |
|
388 | ### Bug Fixes
|
389 |
|
390 | * default '--' to undefined when not provided; this is closer to the array API ([#90](https://github.com/yargs/yargs-parser/issues/90)) ([4e739cc](https://github.com/yargs/yargs-parser/commit/4e739cc))
|
391 |
|
392 |
|
393 |
|
394 | <a name="6.0.0"></a>
|
395 | # [6.0.0](https://github.com/yargs/yargs-parser/compare/v4.2.1...v6.0.0) (2017-05-01)
|
396 |
|
397 |
|
398 | ### Bug Fixes
|
399 |
|
400 | * environment variables should take precedence over config file ([#81](https://github.com/yargs/yargs-parser/issues/81)) ([76cee1f](https://github.com/yargs/yargs-parser/commit/76cee1f))
|
401 | * parsing hints should apply for dot notation keys ([#86](https://github.com/yargs/yargs-parser/issues/86)) ([3e47d62](https://github.com/yargs/yargs-parser/commit/3e47d62))
|
402 |
|
403 |
|
404 | ### Chores
|
405 |
|
406 | * upgrade to newest version of camelcase ([#87](https://github.com/yargs/yargs-parser/issues/87)) ([f1903aa](https://github.com/yargs/yargs-parser/commit/f1903aa))
|
407 |
|
408 |
|
409 | ### Features
|
410 |
|
411 | * add -- option which allows arguments after the -- flag to be returned separated from positional arguments ([#84](https://github.com/yargs/yargs-parser/issues/84)) ([2572ca8](https://github.com/yargs/yargs-parser/commit/2572ca8))
|
412 | * when parsing stops, we now populate "--" by default ([#88](https://github.com/yargs/yargs-parser/issues/88)) ([cd666db](https://github.com/yargs/yargs-parser/commit/cd666db))
|
413 |
|
414 |
|
415 | ### BREAKING CHANGES
|
416 |
|
417 | * rather than placing arguments in "_", when parsing is stopped via "--"; we now populate an array called "--" by default.
|
418 | * camelcase now requires Node 4+.
|
419 | * environment variables will now override config files (args, env, config-file, config-object)
|
420 |
|
421 |
|
422 |
|
423 | <a name="5.0.0"></a>
|
424 | # [5.0.0](https://github.com/yargs/yargs-parser/compare/v4.2.1...v5.0.0) (2017-02-18)
|
425 |
|
426 |
|
427 | ### Bug Fixes
|
428 |
|
429 | * environment variables should take precedence over config file ([#81](https://github.com/yargs/yargs-parser/issues/81)) ([76cee1f](https://github.com/yargs/yargs-parser/commit/76cee1f))
|
430 |
|
431 |
|
432 | ### BREAKING CHANGES
|
433 |
|
434 | * environment variables will now override config files (args, env, config-file, config-object)
|
435 |
|
436 |
|
437 |
|
438 | <a name="4.2.1"></a>
|
439 | ## [4.2.1](https://github.com/yargs/yargs-parser/compare/v4.2.0...v4.2.1) (2017-01-02)
|
440 |
|
441 |
|
442 | ### Bug Fixes
|
443 |
|
444 | * flatten/duplicate regression ([#75](https://github.com/yargs/yargs-parser/issues/75)) ([68d68a0](https://github.com/yargs/yargs-parser/commit/68d68a0))
|
445 |
|
446 |
|
447 |
|
448 | <a name="4.2.0"></a>
|
449 | # [4.2.0](https://github.com/yargs/yargs-parser/compare/v4.1.0...v4.2.0) (2016-12-01)
|
450 |
|
451 |
|
452 | ### Bug Fixes
|
453 |
|
454 | * inner objects in configs had their keys appended to top-level key when dot-notation was disabled ([#72](https://github.com/yargs/yargs-parser/issues/72)) ([0b1b5f9](https://github.com/yargs/yargs-parser/commit/0b1b5f9))
|
455 |
|
456 |
|
457 | ### Features
|
458 |
|
459 | * allow multiple arrays to be provided, rather than always combining ([#71](https://github.com/yargs/yargs-parser/issues/71)) ([0f0fb2d](https://github.com/yargs/yargs-parser/commit/0f0fb2d))
|
460 |
|
461 |
|
462 |
|
463 | <a name="4.1.0"></a>
|
464 | # [4.1.0](https://github.com/yargs/yargs-parser/compare/v4.0.2...v4.1.0) (2016-11-07)
|
465 |
|
466 |
|
467 | ### Features
|
468 |
|
469 | * apply coercions to default options ([#65](https://github.com/yargs/yargs-parser/issues/65)) ([c79052b](https://github.com/yargs/yargs-parser/commit/c79052b))
|
470 | * handle dot notation boolean options ([#63](https://github.com/yargs/yargs-parser/issues/63)) ([02c3545](https://github.com/yargs/yargs-parser/commit/02c3545))
|
471 |
|
472 |
|
473 |
|
474 | <a name="4.0.2"></a>
|
475 | ## [4.0.2](https://github.com/yargs/yargs-parser/compare/v4.0.1...v4.0.2) (2016-09-30)
|
476 |
|
477 |
|
478 | ### Bug Fixes
|
479 |
|
480 | * whoops, let's make the assign not change the Object key order ([29d069a](https://github.com/yargs/yargs-parser/commit/29d069a))
|
481 |
|
482 |
|
483 |
|
484 | <a name="4.0.1"></a>
|
485 | ## [4.0.1](https://github.com/yargs/yargs-parser/compare/v4.0.0...v4.0.1) (2016-09-30)
|
486 |
|
487 |
|
488 | ### Bug Fixes
|
489 |
|
490 | * lodash.assign was deprecated ([#59](https://github.com/yargs/yargs-parser/issues/59)) ([5e7eb11](https://github.com/yargs/yargs-parser/commit/5e7eb11))
|
491 |
|
492 |
|
493 |
|
494 | <a name="4.0.0"></a>
|
495 | # [4.0.0](https://github.com/yargs/yargs-parser/compare/v3.2.0...v4.0.0) (2016-09-26)
|
496 |
|
497 |
|
498 | ### Bug Fixes
|
499 |
|
500 | * coerce should be applied to the final objects and arrays created ([#57](https://github.com/yargs/yargs-parser/issues/57)) ([4ca69da](https://github.com/yargs/yargs-parser/commit/4ca69da))
|
501 |
|
502 |
|
503 | ### BREAKING CHANGES
|
504 |
|
505 | * coerce is no longer applied to individual arguments in an implicit array.
|
506 |
|
507 |
|
508 |
|
509 | <a name="3.2.0"></a>
|
510 | # [3.2.0](https://github.com/yargs/yargs-parser/compare/v3.1.0...v3.2.0) (2016-08-13)
|
511 |
|
512 |
|
513 | ### Features
|
514 |
|
515 | * coerce full array instead of each element ([#51](https://github.com/yargs/yargs-parser/issues/51)) ([cc4dc56](https://github.com/yargs/yargs-parser/commit/cc4dc56))
|
516 |
|
517 |
|
518 |
|
519 | <a name="3.1.0"></a>
|
520 | # [3.1.0](https://github.com/yargs/yargs-parser/compare/v3.0.0...v3.1.0) (2016-08-09)
|
521 |
|
522 |
|
523 | ### Bug Fixes
|
524 |
|
525 | * address pkgConf parsing bug outlined in [#37](https://github.com/yargs/yargs-parser/issues/37) ([#45](https://github.com/yargs/yargs-parser/issues/45)) ([be76ee6](https://github.com/yargs/yargs-parser/commit/be76ee6))
|
526 | * better parsing of negative values ([#44](https://github.com/yargs/yargs-parser/issues/44)) ([2e43692](https://github.com/yargs/yargs-parser/commit/2e43692))
|
527 | * check aliases when guessing defaults for arguments fixes [#41](https://github.com/yargs/yargs-parser/issues/41) ([#43](https://github.com/yargs/yargs-parser/issues/43)) ([f3e4616](https://github.com/yargs/yargs-parser/commit/f3e4616))
|
528 |
|
529 |
|
530 | ### Features
|
531 |
|
532 | * added coerce option, for providing specialized argument parsing ([#42](https://github.com/yargs/yargs-parser/issues/42)) ([7b49cd2](https://github.com/yargs/yargs-parser/commit/7b49cd2))
|
533 |
|
534 |
|
535 |
|
536 | <a name="3.0.0"></a>
|
537 | # [3.0.0](https://github.com/yargs/yargs-parser/compare/v2.4.1...v3.0.0) (2016-08-07)
|
538 |
|
539 |
|
540 | ### Bug Fixes
|
541 |
|
542 | * parsing issue with numeric character in group of options ([#19](https://github.com/yargs/yargs-parser/issues/19)) ([f743236](https://github.com/yargs/yargs-parser/commit/f743236))
|
543 | * upgraded lodash.assign ([5d7fdf4](https://github.com/yargs/yargs-parser/commit/5d7fdf4))
|
544 |
|
545 | ### BREAKING CHANGES
|
546 |
|
547 | * subtle change to how values are parsed in a group of single-character arguments.
|
548 | * _first released in 3.1.0, better handling of negative values should be considered a breaking change._
|
549 |
|
550 |
|
551 |
|
552 | <a name="2.4.1"></a>
|
553 | ## [2.4.1](https://github.com/yargs/yargs-parser/compare/v2.4.0...v2.4.1) (2016-07-16)
|
554 |
|
555 |
|
556 | ### Bug Fixes
|
557 |
|
558 | * **count:** do not increment a default value ([#39](https://github.com/yargs/yargs-parser/issues/39)) ([b04a189](https://github.com/yargs/yargs-parser/commit/b04a189))
|
559 |
|
560 |
|
561 |
|
562 | <a name="2.4.0"></a>
|
563 | # [2.4.0](https://github.com/yargs/yargs-parser/compare/v2.3.0...v2.4.0) (2016-04-11)
|
564 |
|
565 |
|
566 | ### Features
|
567 |
|
568 | * **environment:** Support nested options in environment variables ([#26](https://github.com/yargs/yargs-parser/issues/26)) thanks [@elas7](https://github.com/elas7) \o/ ([020778b](https://github.com/yargs/yargs-parser/commit/020778b))
|
569 |
|
570 |
|
571 |
|
572 | <a name="2.3.0"></a>
|
573 | # [2.3.0](https://github.com/yargs/yargs-parser/compare/v2.2.0...v2.3.0) (2016-04-09)
|
574 |
|
575 |
|
576 | ### Bug Fixes
|
577 |
|
578 | * **boolean:** fix for boolean options with non boolean defaults (#20) ([2dbe86b](https://github.com/yargs/yargs-parser/commit/2dbe86b)), closes [(#20](https://github.com/(/issues/20)
|
579 | * **package:** remove tests from tarball ([0353c0d](https://github.com/yargs/yargs-parser/commit/0353c0d))
|
580 | * **parsing:** handle calling short option with an empty string as the next value. ([a867165](https://github.com/yargs/yargs-parser/commit/a867165))
|
581 | * boolean flag when next value contains the strings 'true' or 'false'. ([69941a6](https://github.com/yargs/yargs-parser/commit/69941a6))
|
582 | * update dependencies; add standard-version bin for next release (#24) ([822d9d5](https://github.com/yargs/yargs-parser/commit/822d9d5))
|
583 |
|
584 | ### Features
|
585 |
|
586 | * **configuration:** Allow to pass configuration objects to yargs-parser ([0780900](https://github.com/yargs/yargs-parser/commit/0780900))
|
587 | * **normalize:** allow normalize to work with arrays ([e0eaa1a](https://github.com/yargs/yargs-parser/commit/e0eaa1a))
|