How to fix npm ERR! code ELIFECYCLE npm ERR! errno SIGTERM npm ERR! process terminated with signal SIGTERM in npm

Q: What does "npm ERR! code ELIFECYCLE npm ERR! errno SIGTERM npm ERR! process termi" mean?

SIGTERM (signal 15) is a termination signal sent to gracefully shut down a process. When npm reports this error, it means an external system (Docker, Kubernetes, CI/CD, or a process manager) sent SIGTERM to your npm process. The issue is that npm doesn't properly forward SIGTERM signals to child processes.

Q: What causes "npm ERR! code ELIFECYCLE npm ERR! errno SIGTERM npm ERR! process termi"?

Docker/Kubernetes sending SIGTERM during container shutdown CI/CD pipeline timeout killing the process Process manager (systemd, PM2) stopping the service

Q: Is the "npm ERR! code ELIFECYCLE npm ERR! errno SIGTERM npm ERR! process termi" error serious?

It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

npmINTERMEDIATEMEDIUMLast verified Dec 6, 2025· 27 views

SIGTERM errors in npm occur when a process is terminated externally, often by Docker, CI timeouts, or process managers. Run Node directly instead of via npm for proper signal handling.

Quick fix

Fixes npm ERR! code ELIFECYCLE npm ERR! errno SIGTERM npm ERR! process terminated with signal SIGTERM

CMD ["npm", "start"]

Run Node directly instead of via npm
Add signal handlers to your application
Use exec form in Dockerfile
Update Procfile for Heroku/similar platforms

npm — error

$CMD ["npm", "start"]
npm ERR! code ELIFECYCLE
npm ERR! errno SIGTERM
npm ERR! process terminated with signal SIGTERM

How to fix "npm ERR! code ELIFECYCLE npm ERR! errno SIGTERM npm ERR! process terminated with signal SIGTERM"

1Run Node directly instead of via npm

The best fix—bypass npm's signal handling issues:

Before (problematic):

dockerfile

CMD ["npm", "start"]

After (correct):

dockerfile

CMD ["node", "index.js"]

This makes your Node.js process PID 1, ensuring it receives signals directly.

2Add signal handlers to your application

Handle SIGTERM in your code for graceful shutdown:

javascript

// At the top of your entry file
process.on('SIGTERM', async () => {
  console.log('SIGTERM received, shutting down gracefully');

  // Close server
  await server.close();

  // Close database connections
  await db.disconnect();

  process.exit(0);
});

process.on('SIGINT', async () => {
  console.log('SIGINT received, shutting down gracefully');
  await server.close();
  process.exit(0);
});

3Use exec form in Dockerfile

Ensure your process receives signals in Docker:

Shell form (bad—signals go to shell, not Node):

dockerfile

CMD npm start

Exec form (good—Node receives signals):

dockerfile

CMD ["node", "index.js"]

Or use ENTRYPOINT:

dockerfile

ENTRYPOINT ["node", "index.js"]

4Update Procfile for Heroku/similar platforms

Use Node directly in your Procfile:

Before:

bash

web: npm start

After:

bash

web: node index.js

5Use process.once for signal handlers

Prevent duplicate signal handling:

javascript

// Use once() instead of on() to handle only first signal
process.once('SIGTERM', shutdownHandler);
process.once('SIGINT', shutdownHandler);

async function shutdownHandler() {
  console.log('Shutting down...');
  // Cleanup code
  process.exit(0);
}

npm can sometimes send signals twice; once() prevents double execution.

6Use a process manager for production

For production deployments, use a proper process manager:

bash

# PM2
pm2 start index.js

# Or in ecosystem.config.js
module.exports = {
  apps: [{
    name: 'app',
    script: 'index.js',
    kill_timeout: 5000
  }]
}

Process managers handle signals correctly and provide additional features like clustering.

How to fix npm ERR! code ELIFECYCLE npm ERR! errno SIGTERM npm ERR! process terminated with signal SIGTERM in npm

Quick fix

What this error means

Typical symptoms

Common causes