# Node.js "cross-env: command not found" in CI

> Fix "cross-env: command not found" in CI - the cross-env binary is missing because devDependencies were pruned or never installed.

Source: https://latchkey.dev/learn/node-js/cross-env-command-not-found-in-ci  
Updated: 2026-06-26

A script uses `cross-env` to set environment variables portably, but the binary is missing in CI. With dev deps pruned (or never installed), the shell cannot find `cross-env` and exits 127.

## 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.js "cross-env: command not found" in CI?

There are 2 common causes: devdependencies pruned in ci and cross-env not declared at all. cross-env is a devDependency.

### How do I fix Node.js "cross-env: command not found" in CI?

There are 2 fixes depending on which cause you have: install cross-env and keep dev deps for builds and set env without cross-env on posix runners. Work through them in order, since the first is the most common.

### What does Node.js "cross-env: command not found" in CI actually mean?

A script that starts with cross-env NODE_ENV=production ...

### How do I stop Node.js "cross-env: command not found" in CI happening again?

Keep devDependencies installed for build jobs. The prevention section lists 3 changes that keep it from recurring.

---

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