# Node "bad option" Unknown Flag in CI - Fix the Node Invocation

> Fix the Node.js "bad option" unknown-flag error in CI by removing the flag, fixing its spelling, or using a Node version that supports it.

Source: https://latchkey.dev/learn/node-js/node-options-bad-option-flag-in-ci  
Updated: 2026-06-26

node: bad option means Node was launched with a flag it does not recognize, often a typo or a newer flag passed to an older Node in CI.

## 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 "bad option" unknown flag in CI?

There are 2 common causes: a flag newer than the ci node version and a typo in a flag or node_options. A flag added in a later Node release is passed to an older runner Node that does not know it.

### How do I fix Node "bad option" unknown flag in CI?

There are 2 fixes depending on which cause you have: pin a node version that supports the flag and fix or remove the flag. Work through them in order, since the first is the most common.

### What does Node "bad option" unknown flag in CI actually mean?

A node invocation in CI exits immediately with node: bad option: <flag>, frequently because NODE_OPTIONS or the command line includes a flag the runner Node does not support.

### How do I stop Node "bad option" unknown flag in CI happening again?

Keep CI Node versions aligned with the flags your scripts need, validate NODE_OPTIONS contents, and only use flags the pinned Node version supports.

---

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