Should hyphenated arguments be expanded into camel-case aliases? Default is true
Should arrays be combined when provided by both command line arguments and a configuration file. Default is false
Should keys that contain . be treated as objects? Default is true
Should arguments be coerced into an array when duplicated. Default is true
Should array arguments be coerced into a single array when duplicated. Default is true
Should parsing stop at the first text argument? This is similar to how e.g. ssh parses its command line. Default is false
The prefix to use for negated boolean variables. Default is 'no-'
Should keys that look like numbers be treated as such? Default is true
Should unparsed flags be stored in -- or _. Default is false
Should a placeholder be added for keys not set via the corresponding CLI argument? Default is false
Should a group of short-options be treated as boolean flags? Default is true
Should aliases be removed before returning results? Default is false
Should dashed keys be removed before returning results? This option has no effect if camel-case-expansion is disabled. Default is false
Should unknown options be treated like regular arguments? An unknown option is one that is not configured in opts. Default is false
Should variables prefixed with --no be treated as negations? Default is
true