Recently, I've been encountering issues with several npm commands failing, accompanied by an error message that looks like this:
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn /usr/bin/zsh
npm ERR! file /usr/bin/zsh
npm ERR! path /usr/bin/zsh
npm ERR! errno ENOENT
npm ERR! <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="a8c5d1f8dac7c2e89886998698">[email protected]</a> preinstall: `npm run myCommand`
npm ERR! spawn /usr/bin/zsh ENOENT
npm ERR!
npm ERR! Failed at the <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="6d00143d1f02072d5d5d5d">[email protected]</a> preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
Upon investigation, it seems that the cause of this error is likely due to the absence of /usr/bin/zsh. In reality, zsh is located within /bin/zsh on my system.
The troublesome script responsible for triggering this error contains:
const { exec } = require('child_process');
exec('npm -v', (err, stdout) => {
if (err) throw err;
if (parseFloat(stdout) < 5) {
// NOTE: This may occur if a dependency specifies an outdated version of npm in its dependencies.
throw new Error(`[ERROR] You need npm version @>=5 but you have ${stdout}`);
}
});
The detailed stack indicates:
17 verbose stack spawn /usr/bin/zsh ENOENT
17 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
17 verbose stack at onErrorNT (internal/child_process.js:415:16)
17 verbose stack at process._tickCallback (internal/process/next_tick.js:63:19)
It appears that child_process is attempting to call /usr/bin/zsh. However, I am uncertain why or how to resolve this issue. Any suggestions?
This dilemma bears resemblance to the one discussed here: Trying to run concurrently (npm ERR! code ELIFECYCLE npm ERR!)
Despite a full reinstallation of node, npm, and nvm, the problem persists. The error also manifests when using yarn.
Another puzzling observation:
I am unable to locate internal/child_process.js or internal/process/next_tick.js anywhere.
Edit: Regardless of the executed script, this error occurs consistently.
If I execute a script npm run x, which is defined in package.json as "x"="npm run y", it fails. However, running npm run y directly functions as expected.