EBADENGINE Node.js Origin: Application & API Last updated 13 Oct 2026

npm WARN EBADENGINE Unsupported engine / The engine "node" is incompatible with this module

A package requires a different Node.js version than the one you’re running.

Exact message you may see Unsupported engineThe engine "node" is incompatible with this module
Seen on: Node.js

Meaning

package.json "engines" declares supported versions. npm warns (EBADENGINE); yarn and pnpm can fail. Running anyway may break at runtime.

Common causes

  • Node too old for a dependency
  • Node too new for a legacy package
  • CI using a different Node version than local

⚡ Quick fix

  1. Switch Node version with nvm (nvm use 20)
  2. Add .nvmrc to the project
  3. Pin Node in CI (setup-node)

Detailed fix by platform

Node.js

  1. echo "20" > .nvmrc && nvm use

How to diagnose

  1. Required — Version range in the message
  2. Current — node -v

🔧 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: Application & API. Errors that are often confused with or caused by this one (click to open):

0x8007007E — 0x8007007E: The specified module could not be found (Windows)0x8007007ECould not resolve — Gradle: Could not resolve all files for configuration / Could not resolve dependency (Android)Could not resolveDEP0005 — DeprecationWarning: Buffer() is deprecated due to security and usability issues (DEP0005) (Node.js)DEP0005DEP0040 — DeprecationWarning: The `punycode` module is deprecated (DEP0040) (Node.js)DEP0040Dependency requires compileSdk — Dependency 'androidx.x:1.y' requires libraries and applications that depend on it to compile against version 34 or later of the Android APIs (Android)Dependency requires c…Duplicate class — Duplicate class X found in modules A and B (Android)Duplicate classERR_PACKAGE_PATH_NOT_EXPORTED — Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './x' is not defined by "exports" (Node.js)ERR_PACKAGE_PATH_NOT_…held broken packages — Unmet dependencies / E: Unable to correct problems, you have held broken packages (Linux)held broken packagesEBADENGINE

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.