docopt.coffee

docopt.coffee copied to clipboard

```js const options = docopt( ` Usage: foo [options] --bar Description `, { argv: ['--bar'] } ); ``` Throws because it doesn't detect `--bar` as an option. Looking at the...

Shakeskeyboarde

lurch

Is this published on NPM?

2

It points to a different repo: https://www.npmjs.com/package/docopt

metasansana

Docopt breaks lots of JS modules.

3

Due to Docopt manipulating native objects' prototypes, it breaks lots of modules that rely on the standard behaviour. Right now, it isn't safe to use Docopt with any other module,...

robotlolita

Add JS usage section to readme

1

Hi. It was non-obvious to me how I would use this from JS, so I thought I'd update the docs to add a little usage section. Let me know what...

aviddiviner

Hi there! It would be useful to add environment variables support. Consider this example: https://robpol86.github.io/docoptcfg/fix_repeating/env_vars.html

stepankuzmin

The following example prints the usage and exits, instead of correctly parsing the arguments. ```js const {docopt} = require("docopt") const usage = ` A description for my_program Usage: my_program (--param1...

jrop

Docopt seems to erroneously repeat arguments when parsing an option block when: - it is a repeating option. - it has multiple matching options in the same '[ ]' block....

rgrannell1

"throw" errors instead of trying to "raise" them

1

The Coffee Script port says `raise` when it means `throw`, the valid ECMAScript keyword for error-raising statements. I'm guessing the test suite checks only that an error is raised, but...

kemitchell

https://docs.npmjs.com/files/package.json#license http://npm1k.org/

pdehaan