How to fix npm ERR! code ELIFECYCLE npm ERR! errno 130 npm ERR! Exit status 130 in npm

If you pressed Ctrl+C, exit code 130 is correct:

^C   <-- You pressed Ctrl+C
npm ERR! code ELIFECYCLE
npm ERR! errno 130

This is expected. The process stopped exactly as you requested. npm just reports all non-zero exits as errors.

For development servers, you can safely ignore this message. The server stopped, which is what you wanted.

If it bothers you, you can suppress the error output:

npm start 2>/dev/null || true

To exit cleanly with code 0 instead of 130:

process.on('SIGINT', () => {
  console.log('\nGracefully shutting down...');
  // Cleanup code here
  process.exit(0);
});

This prevents the non-zero exit code.

Puppeteer can intercept SIGINT. Disable it:

const browser = await puppeteer.launch({
  handleSIGINT: false
});

This prevents Puppeteer from calling process.exit() when you press Ctrl+C.

If CI fails on exit 130 when it shouldn't:

GitHub Actions:

- run: npm start &
- run: sleep 10
- run: kill -2 $!  # This will exit 130, which is fine
  continue-on-error: true

Or check the exit code explicitly in scripts.

nodemon v1.18.1+ explicitly exits with 130 on SIGINT. If this causes issues:

npm install [email protected] --save-dev

Note: This is an older version and may have other issues with newer Node.js versions.