On Windows 7 x64: '\"node web.js\"' is not recognized as an internal or external command... about node-foreman

[rmg]

Sadly, this is probably a result of cae06b9 which was the fix for #49.

Since that was the only real change in 0.4.1, you can try 0.4.0 with npm install -g [email protected]. It will eventually crash, if it runs long enough, but normal developer work flow usually involves killing it before that happens anyway.

[davidmurdoch]

Just FYI, if you remove the quotation marks (and the /s switch) it works.

It looks as if node's spawn actually escapes quotation marks in args, which means the /s switch never gets to do anything.

I think args = ['/c', proc.command]; should do the trick.

[rmg]

@davidmurdoch any chance you could verify that? I don't have a real Windows machine, so it might be faster for you.

[rmg]

Found a Windows VM, publishing a patch release momentarily.

[davidmurdoch]

Sorry, I was away for a moment.

I knew it works for my node web.js case; I just hadn't tested more complex scenarios involving quotes and/or nested quotes, that's why I said that "I think".

Glad I could help track this down and thanks for the quick responses!

[rmg]

Forgot to say the publish was done. v0.4.2 was released with the fix.