Since you're assuming that process.env.SHELL is set, which may or may not be the case on Windows.
But if/when it is available on Windows, then it's usually a unix-style path such as /bin/bash. This path isn't gonna work on Windows' cp.spawn() and will result in a error spawn ENOENT error.
Some possible (combinations of) solutions:
Just use cmd.exe on Windows.
Detect when we are running from within a "cygwin" environment and conver the "SHELL" env variable to a cygwin path. This should be relatively easy.
This would only really leave detecting git-bash and its path resolution, but that's not really important for us ATM.
Since you're assuming that
process.env.SHELL
is set, which may or may not be the case on Windows.But if/when it is available on Windows, then it's usually a unix-style path such as
/bin/bash
. This path isn't gonna work on Windows'cp.spawn()
and will result in aerror spawn ENOENT
error.Some possible (combinations of) solutions:
cmd.exe
on Windows.git-bash
and its path resolution, but that's not really important for us ATM.I'll probably try to whip up a patch for 1+2.