I got an error during deployment, as follows:
npm ERR! npm WARN using --force Recommended protections disabled.
npm ERR! npm WARN ERESOLVE overriding peer dependency
npm ERR! npm WARN ERESOLVE overriding peer dependency
npm ERR! npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm ERR! npm WARN deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead
npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm ERR! npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm ERR! npm WARN deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead
npm ERR! npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm ERR! npm ERR! code 127
npm ERR! npm ERR! path /vercel/.npm/_cacache/tmp/git-cloneXXXXXXjxBJvU/node_modules/zlib
npm ERR! npm ERR! command failed
npm ERR! npm ERR! command sh -c node-waf clean || true; node-waf configure build
npm ERR! npm ERR! sh: line 1: node-waf: command not found
npm ERR! npm ERR! sh: line 1: node-waf: command not found
npm ERR!
npm ERR! npm ERR! A complete log of this run can be found in: /vercel/.npm/_logs/2024-07-16T00_07_23_336Z-debug-0.log
npm ERR! A complete log of this run can be found in: /vercel/.npm/_logs/2024-07-16T00_07_04_303Z-debug-0.log
Error: Command "npm install" exited with 127
I got confused about this error. I don’t use node-waf
, but somehow, I got a message that node-waf: command not found
.
Could you please help me to solve this issue?
Solideo Putra Zendrato is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
One of your dependencies uses node-waf
, you don’t need it specified in your package.json, that’s how dependency lists become so huge.
What you want to do is find out which of your dependencies uses node-waf
and update that dependency. It looks like zlib
uses it, but that might be another sub-dependency of one of your main dependencies.
This command shows you the dependency tree and allows you to see which base dependency uses the wrong sub-dependency:
npm ls --all
What you then want to do is update your dependency and hope that solves the issue. Or replace that dependency with something completely new and updated if it is poorly maintained.
1