CLI doesn't work with single quotes on windows

[ismay]

When using the CLI from package.json this fails:

// ...
  "scripts": {
    "watch": "watch 'npm run start' src"
  },
// ...

With the following error:

> "watch 'npm run start' src
> Watching 'npm
> Watching run
> Watching start'
C:\Projects\simple\node_modules\watch\main.js:73
    if (err) throw err;
             ^

Error: ENOENT: no such file or directory, stat 'C:\Projects\simple\'npm'
    at Error (native)

But this does:

// ...
  "scripts": {
    "watch": "watch \"npm run start\" src"
  },
// ...

Being used to *nix this was a bit of a surprise. Don't know if this is expected behaviour on windows, or a bug, but just thought I'd report it.

[levithomason]

This is indeed a windows limitation. Your escaped double quote solution is the correct approach.

EDIT

To clarify, I mean to say it is entirely unrelated to watch. On Windows when using quotes in scripts you need to use double quotes due to how Windows handles them on the command line.

[ismay]

Ok cool, thanks!

[levithomason]

No problem, thanks for the report.