Node 10 - `Node-Gyp Rebuild` Error During Npm Install
I've Recently Upgraded to Node 10 and When I Run Npm Install I Get the Following Error: Make: *** [Release/ Error 1 Gyp Err! Build Error Gyp Err! Stack Error...
I've recently upgraded to Node 10 and when I run npm install I get the following error:
make: *** [Release/ Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack at ChildProcess.emit (events.js:182:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
gyp ERR! System Darwin 18.2.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/david/Documents/gitlab/project/node_modules/memwatch-next
gyp ERR! node -v v10.15.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! memwatch-next@0.3.0 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the memwatch-next@0.3.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Working on 'macOS Mojave', I worked on the same project with Node10 without any issues. Please advise what can be causing the error?
6 Answers
Resolved the issue by updating npm to latest version & running npm rebuild.
Use NVM for managing node. It is really helpful. I had the same error but solved it by using the latest Node LTS version. That can be done with NVM easily by a single command.
nvm install --lts
without knowing the actual node-gyp error, make sure you've installed the node-gyp dependencies for your platform.
I think delete this directory is better:
rm -rf ~/.node-gyp/
rm -r node_modules/.bin/;
rm -r build/
and you can test
npm install -g node-gyp
and
npm install -g node-pre-gyp
finally:
npm install <your module>
I had the same issue & it was solved by deleting the yarn.lock file & then running the yarn install again
I had the same problem. First I removed package.json and run npm install but it doesn't help. Only a return to the previous stable node version helped me. (nvm is very useful)
Alexander Ross has covered the video game industry for a decade, writing deep dives on game design, esports tournaments, VR developments, and gaming culture.
