"'npm' is not recognized as an internal or external command, operable program or batch file" about parallelshell

[jlbruno]

orrr I could be way off and it was trying to call the command as 'npm instead of npm

:)

Still not sure if maybe it's a windows thing? Changed my package.json to this:

`"start": "parallelshell \"npm run watch:browser-sync\" \"npm run watch:sass\"",

and it seems to now call the tasks, but browser-sync doesn't seem to be working now dammit.

[jlbruno]

Wondering if it's related to this?
nodejs/node-v0.x-archive#2318

In this issue on grunt, they recommend using node-which
gruntjs/grunt#155
https://github.com/isaacs/node-which/

[keithamus]

Hmm, that's irritating. Thanks for the issue @jlbruno. Looks like https://github.com/keithamus/parallelshell/blob/master/index.js#L14 needs to change from exec(childCmd to exec(isWin ? 'cmd' : 'sh'.... Or perhaps just depend on https://github.com/IndigoUnited/node-cross-spawn.

If you'd like to @jlbruno, a PR would be very much welcome. Otherwise I'll work on this over the weekend.

[keithamus]

Ahh, interesting. I made the assumption single quotes would work in the Windows command line. Silly me.

I'll close this one for now then. If you want some help with npm scripts in general, I'm hanging out in https://gitter.im/keithamus/npm-run-scripts and can help 😄

[dlockhart]

I just ran into this same issue and switching from single to double quotes solved it for me on Windows. Lots of other issues with watch libraries like onchange and their handling of using child_process.spawn to run npm, but that's outside the scope of parallelshell. :)

[jlbruno]

Do the double quotes work on mac as well? If so, I'd be happy to send a PR to update the readme file with double instead of single quotes, but I have no mac to test on.

[dlockhart]

Double quotes do indeed work on Mac! :)

[keithamus]

@jlbruno please feel free to send a PR updating to double quotes. They will work in bash, but it should be noted that they are interpreted for variables and globs (e.g. "*" is expanded before being passed, while '*' isn't).

[olowoseun]

I'll just stick to using double quotes whenever I'm working in a scripting environment on Windows! 😉