Failure to spawn certain processes on Windows
jankolkmeier opened this issue · comments
I am having an issue on windows when trying to spawn ruby processes like compass or sass. I haven't tracked down the exact issue, but it seems related to this: nodejs/node-v0.x-archive#2318
I have applied the proposed fix (commit incoming) and it seems to work well in my case. I don't have time/setup to give a throughout test, though.
same issue here (with docpad-plugin-sass) and I confirm that the fix works for me
With the just released v1.4.1 you can now use getExecPath
to get the full path of an executable, you would then use that path when doing your exec or spawn calls. Will update the docpad plugins to make use of this.