home/someuser/.nvm/versions/node/v9.5.0/include/node/v8-profiler.h Example: /home/someuser/.nvm/versions/node/v9.5.0/include/node/v8-platform.h Unless it was getting v8 from the include/node directory of v9 installations.
Still not sure where it was getting the v8 from. Strange issue and looks like some users ran into similar issues with using nvm resources in bash based on this thread. So apparently the nvm isn't available in shell-scripts env without sourcing it and the npm run build needs to see nvm. Next I removed source ~/.nvm/nvm.sh and it was broken again. Note the source ~/.nvm/nvm.sh #!/bin/shĪt one point I had nvm use v9.5.0 and then tested it still works without it. Despite the fact that node -v for someuser was returning v9.4.0 and the locate command not finding any v8 versions installed for any user, and having re-installed node, i was still getting the same error. Per Olorin's suggestion to look at the node error, I explored that more. That last attempt returns same as first: git commands work, build throws errors about sass and environment as if something is different than when i run the command as the user from the terminal.Īny idea why this command is not working correctly? I though that the user -c would set me up with all env like the user was logged in and that env -i would give me clean env without the parent. So i then tried env -i /usr/local/bin/npm run build and oddly that returned /usr/bin/env: 'node': No such file or directory. I even tried env -i npm run build in the script and that just says env: ‘npm’: No such file or directory. If I run npm run build as the user from terminal, everything builds fine. Run `npm rebuild node-sass -force` to build the binding for your current environment.
This usually happens because your environment has changed since running `npm install`. The npm command runs and builds the files but throws lots of errors about Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 8.xįound bindings for the following environments: I have a script that runs some git and npm commands based on a user like #!/bin/sh
0 kommentar(er)
