# Node "spawn ENOENT" for a Child Process in CI - Fix the Missing Executable

> Fix the Node.js "spawn ENOENT" child-process error in CI by installing the missing executable or correcting the command name and PATH on the runner.

Source: https://latchkey.dev/learn/node-js/node-spawn-enoent-child-process-in-ci  
Updated: 2026-06-26

spawn ENOENT means child_process could not find the executable you asked it to run. The binary is not on PATH on the CI runner.

## Diagnose it: the shell in CI is not your shell

Package scripts run under a different shell, a different PATH, and a non-interactive environment on a runner. Most scripts that fail only in CI are relying on something the login shell gave them locally: a tool on PATH, an environment variable from a dotfile, or a TTY.

```Terminal
# what the script can actually see
npm run env | grep -E "^(PATH|NODE_ENV|CI)=" 

# is the binary on PATH for the script, not just for you?
npm exec -- which <tool> || echo "not resolvable from npm scripts"

# run the exact script with tracing
sh -x -c "$(node -p "require('./package.json').scripts.build")"
```

> A tool installed globally on your machine but only a devDependency in the repo works locally and fails in CI. Call it through `npm exec` or a `node_modules/.bin` path rather than assuming it is on PATH.

## Make failures fail the job

A multi-command script can report success while a middle command failed, which produces the worst kind of CI result: a green build that shipped something broken.

```.github/workflows/ci.yml
# pipefail is NOT set by default in every runner shell
- name: Build
  shell: bash
  run: |
    set -euo pipefail
    npm run build | tee build.log
```

> Without `pipefail`, the exit status of a pipeline is the status of the LAST command, so `failing-command | tee log` reports success. Piping build output to a log file is exactly where this bites.

## FAQ

### What causes Node "spawn ENOENT" for a child process in CI?

There are 2 common causes: the executable is not installed on the runner and a typo or a shell builtin spawned without a shell. The CI image lacks the binary the child process invokes, so spawn cannot locate it.

### How do I fix Node "spawn ENOENT" for a child process in CI?

There are 2 fixes depending on which cause you have: install the executable in ci and run shell builtins through a shell. Work through them in order, since the first is the most common.

### What does Node "spawn ENOENT" for a child process in CI actually mean?

A node process that shells out throws Error: spawn <command> ENOENT.

### How do I stop Node "spawn ENOENT" for a child process in CI happening again?

Install every external binary your scripts spawn as an explicit CI setup step, verify command names, and prefer absolute paths or shell: true where appropriate.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt