Expected Behavior:
I don't have grunt globally, and I'm not using it like that, as different projects require different versions and tools.
I expect to be able to run grunt that is installed with CMB2 using npm run grunt * instead of see below.
Actual Behavior:
I need to install grunt-cli of older version 0.1.13.
I have to type node ./node_modules/grunt-cli/bin/grunt * to be able to run it.
I can't use ./node_modules/.bin/grunt* because it's platform specific, for *mix I will need ./node_modules/.bin/grunt, for Windows: ./node_modules/.bin/grunt.cmd. And it will be overkill to add both to package.json>scripts>grunt & package.json>scripts>grunt_win. So that' why a "node" direct call should be used.
Expected Behavior:
I don't have grunt globally, and I'm not using it like that, as different projects require different versions and tools.
I expect to be able to run
gruntthat is installed with CMB2 usingnpm run grunt *instead of see below.Actual Behavior:
I need to install
grunt-cliof older version0.1.13.I have to type
node ./node_modules/grunt-cli/bin/grunt *to be able to run it.I can't use
./node_modules/.bin/grunt*because it's platform specific, for *mix I will need./node_modules/.bin/grunt, for Windows:./node_modules/.bin/grunt.cmd. And it will be overkill to add both to package.json>scripts>grunt & package.json>scripts>grunt_win. So that' why a "node" direct call should be used.