No warning when incorrect options are passed with changed parameters order

[GoalSmashers]

Let's take the following code (assume file is named demo.js).

#!/usr/bin/env node

var commands = require('commander');

commands
  .option('-t, --test <value>', 'Just testing')
  .parse(process.argv);

Let's try to run it:
./demo.js --test 5 - no errors
./demo.js --test 5 demo.js - no errors
./demo.js --test 5 --test2 demo.js - unknown option '--test2'
./demo.js demo.js --test 5 --test2 - no errors

Apparently extra arguments where added at the beginning suppress errors.

[nitoyon]

This bug is fixed by my pull request #121.
I hope @visionmedia would merge it.

[GoalSmashers]

Perfect, thanks a lot!

[nitoyon]

If you aren't using command(), see this quick hack: nitoyon/livereloadx@5215812.
I'm avoiding this bug by using lower API of commander.js.

[GoalSmashers]

That's a nice bit. We'll check that or maybe your patch will get pulled in the meantime. Thanks for sharing!

[shadowspawn]

This issue has not had any activity in over six months. It isn't likely to get acted on due to this report.

Feel free to open a new issue if it comes up again, with new information and renewed interest.

Thank you for your contributions.