Closed danielkhan closed 6 years ago
Are you running on Windows? It looks like the compile script is bash-specific. @djonathascardoso would you mind looking into this?
Probably is a problem with Windows. @danielkhan could you confirm your OS?
@djonathascardoso I was able to re-produce this on Windows. We should rethink the process for having multiple commands in a single script, since ;
is not portable (also, it ignores exit code values).
I ran into this as well. Definitely Windows specific. Quick and easy workaround is to use WSL/Bash on Windows https://docs.microsoft.com/en-us/windows/wsl/install-win10
;
vs &&
isn't the only problem. There's also reliance on POSIX tools like cp
Yes I can confirm that this happened on a windows machine. Thank you for the swift response.
@OsvaldoRosado @danielkhan Thanks for the responses. Supporting Windows is important (after all, we don't want to be restrictive on the platform) but at this early stage we haven't had a chance to fully test things out on Windows.
I will go through the npm scripts and make changes that will be more cross-platform, but I think some more complex commands might need to warrant a longer-term solution.
On a fresh clone, running npm install exits with an error