Incorrect parsing of multiple options with no value about grunt-cli HOT 4 CLOSED

I just get a weird issue this morning
spawning grunt from a node js script with args below give me the Fatal error: Unable to find local grunt.

[ 'happyplan:dist',
  '--verbose',
  '--gruntfile',
  './node_modules/happyplan/Gruntfile.js',
  '--base',
  '/Users/MoOx/Sync/Development/putaindecode/website' ]

Just changing the order fix that.

[ '--gruntfile',
  './node_modules/happyplan/Gruntfile.js',
  '--base',
  '/Users/MoOx/Sync/Development/putaindecode/website',
  'happyplan:dist',
  '--verbose' ]

Is this a normal behavior ?

from grunt-cli.

This is an issue with how the nopt library parses these flag parameters.
It was fixed in v2.0.0 (July 2012) so it might be worth updating to a newer version of nopt to fix this.

Edit:
Interestingly, nopt needs to be updated in both the grunt-cli and grunt project, but it does seem to fix the problem.

Edit 2:
This is a known issue in Grunt: gruntjs/grunt#908
It's expected to be fixed in a future release (e.g. 0.5) because it's a breaking change for some people.

@unknpwn's workaround is probably the easiest way of handling this until it's fixed.

$ grunt migrate --dryrun=1 --rollback=1

from grunt-cli.

I can confirm that behaviour. Fingers crossed for a resolution in a future release!

from grunt-cli.

Fixed when nopt was updated (0928d68) and will get released soon. Thanks for your patience!

from grunt-cli.