Node.js version detected. The Angular CLI requires a minimum Angular Origin: On your device Last updated 15 Oct 2026

Angular CLI: Node.js version v16.20.2 detected. The Angular CLI requires a minimum Node.js version of v18.19.1

Your Node.js is older (or newer, unsupported) than the Angular CLI version needs.

Exact message you may see Node.js version detected. The Angular CLI requires a minimumThe Angular CLI requires a minimum Node.js versionNode.js version v16 detectedNode.js version is not supported by Angular CLINode.js version v21
Explore the map of this error Full error map →
Seen on: Angular Angular CLI Node.js

Meaning

Each Angular major supports specific Node versions (for example Angular 18 needs Node 18.19+ or 20.11+). Use a version manager (nvm, fnm, Volta) to switch Node, or upgrade/downgrade Angular to match the Node you must use.

Common causes

  • Node older than the CLI minimum
  • Odd-numbered (non-LTS) Node such as 21 or 23
  • Project pinned to an old Angular but a newer global CLI used
  • CI image with an outdated Node
  • Windows/WSL using a different Node than expected

⚡ Quick fix

  1. Switch Node with nvm use 20 (or fnm/Volta)
  2. Add .nvmrc and engines to the project
  3. Use the CLI version that matches your Angular version

Detailed fix by platform

Linux

  1. nvm install 20 && nvm use 20 && node -v then reinstall the CLI if it was global
  2. Pin: echo 20 > .nvmrc

Windows

  1. Use nvm-windows or Volta: volta install node@20

How to diagnose

  1. Versions — node -v and ng version?
  2. Support — Node range for this Angular major?
  3. Environment — Same Node in CI and local?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

Could not find the builder's node package — Angular CLI: Could not find the '@angular-devkit/build-angular:browser' builder's node package / Cannot find module '@angular-devkit/build-angular/package.json' (Angular)Could not find the bu…EBADENGINE — npm WARN EBADENGINE Unsupported engine / The engine "node" is incompatible with this module (Node.js)EBADENGINEERESOLVE peer dependency conflict after ng update — Angular: npm ERR! ERESOLVE could not resolve — Conflicting peer dependency: @angular/core@"^16.0.0" (after ng update / ng add) (Angular)ERESOLVE peer depende…exceeded maximum budget — Angular build: Error: bundle initial exceeded maximum budget. Budget 1.00 MB was not met by 120.00 kB with a total of 1.12 MB (Angular)exceeded maximum budg…ng: command not found — Angular CLI: zsh: command not found: ng / 'ng' is not recognized as an internal or external command (Angular)ng: command not foundPort 4200 is already in use — Angular CLI: Port 4200 is already in use. Use '--port' to specify a different port (Angular)Port 4200 is already …Repository is not clean — Angular CLI: Repository is not clean. Please commit or stash any changes before updating. (Angular)Repository is not cle…Schema validation failed with the following errors — Angular CLI: Schema validation failed with the following errors: Data path "" must NOT have additional properties(xyz) (Angular)Schema validation fai…Node.js v…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.