How to fix npm ERR! Error: spawn ENOENT in npm

The error message often does not show which command failed. Re-run npm with verbose logging using the correct flag (--loglevel verbose, or its alias -d):

npm install --loglevel verbose
# or for a script
npm run your-script --loglevel verbose

Scan the output for the failing command name near the spawn ENOENT line. You can also turn on npm's internal debug logging:

# Linux/macOS
NPM_CONFIG_LOGLEVEL=silly npm install

# Windows PowerShell
$env:NPM_CONFIG_LOGLEVEL="silly"; npm install

Then open the package.json "scripts" section and check which command might be unavailable on your system. The npm debug log at the path printed in the error (e.g. ~/.npm/_logs/...-debug-0.log) also records the exact command.

Once you know which command is failing, confirm it is installed and on PATH:

# Linux/macOS
which git
which python3

# Windows Command Prompt
where git
where python

# Windows PowerShell
Get-Command git
Get-Command python

If it is not found, install it:

# macOS (Homebrew)
brew install git python

# Ubuntu/Debian
sudo apt-get install git python3

# Windows (Chocolatey)
choco install git python

Open a new terminal afterward so the updated PATH is loaded.

On Windows, a missing PATH entry is a common cause. Verify these directories are present:

1. Open System Properties > Advanced > Environment Variables
2. Under "System variables", edit "Path"
3. Confirm entries such as:
- C:\Windows\System32
- C:\Windows
- C:\Program Files\Git\cmd (if using Git)
- C:\Program Files\nodejs\

You can also add an entry for the current session, or persist it with setx (note: setx truncates values longer than 1024 characters and does not affect the current session — prefer the GUI for permanent changes):

# Add to PATH for the current session only
$env:Path += ";C:\Program Files\Git\cmd"

# Persist for future sessions (user PATH)
setx PATH "$env:Path;C:\Program Files\Git\cmd"

Restart your terminal after making permanent changes.

A corrupted or partial install can leave binaries missing. Do a clean reinstall:

# Remove installed packages and the lockfile
rm -rf node_modules
rm package-lock.json

# Reinstall dependencies
npm install

On Windows, if deletion fails due to locked files or long paths:

npx rimraf node_modules
npm install

If the problem persists, verify the npm cache (this checks and repairs cache integrity without deleting valid data):

npm cache verify

Only clear the cache fully if a corrupt cache is suspected, since --force is normally discouraged by npm:

npm cache clean --force

Some packages compile native code during install and need a C/C++ toolchain plus Python. Install the appropriate tools for your platform.

Windows:

The old windows-build-tools npm package is deprecated and unmaintained — do not use it; it commonly fails on current systems. Instead, use one of these supported options:

- During Node.js installation, check "Automatically install the necessary tools... (Tools for Native Modules)" in the official installer, or
- Install the Visual Studio Build Tools directly with the "Desktop development with C++" workload from https://visualstudio.microsoft.com/downloads/, or via winget:

winget install Microsoft.VisualStudio.2022.BuildTools

Modern Node.js bundles a recent Python, so a separate Python install is usually unnecessary.

macOS:

xcode-select --install

Linux (Debian/Ubuntu):

sudo apt-get install build-essential python3

Linux (RHEL/CentOS/Fedora):

sudo dnf groupinstall "Development Tools"

If node-gyp cannot find Python, point it at the right interpreter:

npm config set python /usr/bin/python3

If scripts fail on one OS but not another, use cross-platform helpers instead of shell-specific syntax.

cross-env for environment variables:

npm install --save-dev cross-env

{
  "scripts": {
    "build": "cross-env NODE_ENV=production webpack"
  }
}

shx for shell-style file commands:

npm install --save-dev shx

{
  "scripts": {
    "clean": "shx rm -rf dist"
  }
}

cross-spawn when you call spawn from your own Node.js code (it fixes Windows .cmd/.bat and PATHEXT resolution):

npm install cross-spawn

const spawn = require('cross-spawn');

const result = spawn.sync('npm', ['install'], { stdio: 'inherit' });

Slim base images and CI runners often lack the shell or tools your scripts expect.

Docker — install what the scripts need:

# Alpine ships ash, not bash, and omits many tools
FROM node:20-alpine

RUN apk add --no-cache bash git

Spawning from Node.js code: passing shell: true lets the system shell resolve the command via PATH/PATHEXT, which often fixes ENOENT (be aware that with shell: true you must avoid passing untrusted input, since it is interpreted by the shell):

const { spawn } = require('child_process');

spawn('npm', ['install'], {
  shell: true,
  stdio: 'inherit'
});

CI examples:

GitHub Actions — pin the shell:

- name: Install dependencies
  shell: bash
  run: npm install

GitLab CI — install missing tools first:

before_script:
  - apt-get update && apt-get install -y git