"Fossies" - the Fresh Open Source Software Archive

Member "Atom/resources/app/apm/node_modules/dashdash/CHANGES.md" (8 Dec 2016, 10912 Bytes) of archive /windows/misc/atom-windows.zip:


As a special service "Fossies" has tried to format the requested source page into HTML format (assuming markdown format). Alternatively you can here view or download the uninterpreted source code file. A member file download can also be achieved by clicking within a package contents listing on the according byte size field.

node-dashdash changelog

not yet released

(nothing yet)

1.14.1

1.14.0

1.13.1

1.13.0

1.12.2

This is a bit of a hack, but IMO a better experience than the surprise of matching a local filename beginning with 'z', which isn't, in this case, a "fruit".

1.12.1

1.12.0

1.11.0

We could define an option type for --foo such that opts.foo = ['a', 'b', 'c']. See "examples/custom-option-arrayOfCommaSepString.js" for an example.

1.10.1

1.10.0

1.9.0

1.8.0

1.7.3

Before this change, that would not parse correctly. It is suspected that this was introduced in version 1.4.0 (with commit 656fa8bc71c372ebddad0a7026bd71611e2ec99a).

1.7.2

1.7.1

to render as a blank line in option help. This can help separate loosely related sets of options without resorting to a title for option groups.

1.7.0

1.6.0

will give you this help output:

    ...
      Armament Options:
        -w, --weapon

      General Options:
        -h, --help
    ...

1.5.0

A custom option type is added via:

    var dashdash = require('dashdash');
    dashdash.addOptionType({
        name: '...',
        takesArg: true,
        helpArg: '...',
        parseArg: function (option, optstr, arg) {
            ...
        }
    });

1.4.0

See 'allowUnknown' in the README for a subtle caveat.

1.3.2

wanted FOO_VERBOSE=0 to make the option false, then you need the fix in this version of dashdash.

1.3.1

1.3.0

1.2.1

1.2.0

1.1.0

1.0.2

1.0.1

1.0.0

First release.