rstacruz/rminimist

Parse argument options

rminimist's Issues

*Too* restrictive on argument-names

I love the idea of rminimist — deterministic parsing of the command-line without aggressive and paranoid configuration, with the intuitive and simple-JavaScript-y style of minimist? yes please.

However, rminimist is currently way too restrictive about flags' names … at least, in my very-humble-opinion. All of these are invalid, and are just going to be completely ignored by rminimist, even if they're explicitly typed by the configuration-object:

$ script.js -@ --passé --a-longer-flag

Of course, I can construct arbitrarily-pathological examples, but those three seem to summarize a few relatively-reasonable use-cases that rminimist is currently broken for.

Is this outside of rminimist's scope, or might it be a welcome fix?

Publish latest version?

Currently I'm trying to setup hledger-vis, but fails because [email protected] doesn't seem to be published

npm ERR! No compatible version found: [email protected]
npm ERR! Valid install targets:
npm ERR! 1.0.1, 1.0.0

Also, I checked the npm page:

Probably just needs the version to be published?