amagura/bebopt

a more powerful option parser for node.js

bebopt's Issues

0.1 - Features

Supported Features - v0.1

• parses short options (e.g. -h, -v)
• parses long options (e.g. --help, --version)
• parses shortLong options (e.g. -help, -version)
• supports long, short, and shortLong options (e.g. .longBeat(), .shortBeat(), .halfBeat())
• supports both major forms of option-argument specification (e.g. --help=<ARG> and --help <ARG>)

UglifyJS2 has been identified to contain a security risk

Issue

Apparently there's some kind of security risk in UglifyJS2 v2.0.0 (or whatever version Bebopt uses); I need to either remove it from Bebopt or upgrade the one that Bebopt depends upon.

README with indexes

I think it'd really help set bebopt apart if its README had an index. Every option parser I've come across on github leaves the toil of having to wander through endless READMEs to the unsuspecting traveler.

This, of course, implies that I'll have to re-write the README in asciidoc...

known short options are accepted when passed as long options

If -x is a known short option, bebopt, in its current form, will accept --x. I don't think that very many people use Bebopt, which is perfectly understandable, seeing that Bebopt is such a young library and hardly production ready, all the same, I'm in no rush to fix this bug. I don't really write programs in JavaScript very much, since other languages are far more suitable for writing applications than JS, so unless somebody else would like to use Bebopt more and would like me to fix it, or has already fixed it for me 😉, I might be obliged to do something about it.