npm ERR! code EBADENGINE

What This Error Means

The package requires a different Node.js/npm version than the one you are using (engine mismatch).

How to Fix It

1. Check your current versions: node -v and npm -v.
2. Check required engines: npm view <pkg>@<version> engines.
3. Switch Node.js version (example: nvm use <version>), then reinstall.
4. Retry with npm --verbose if the error message is truncated.

Why It Happens

• The configured registry does not contain the package/version you requested.
• Auth is missing for a private registry or scoped package.
• The requested version/tag/range is invalid or does not exist.

How to Verify

1. Re-run npm view <pkg> for the same registry and confirm metadata is accessible.
2. Re-run the original install and confirm the resolution error no longer appears.

Manual dependency inspection

1. Check which registry npm is using: npm config get registry.
2. If the package is scoped, verify scope registry mapping in .npmrc (example: @your-scope:registry=...).
3. Query the registry directly for metadata: npm view <pkg>@<version> --json.

Common CLI Output

npm ERR! code EBADENGINE

npm ERR! engine Unsupported engine

How npm resolves dependencies

1. npm resolves packages by fetching metadata from the registry, then selecting versions that satisfy semver ranges.
2. Private registries and scopes add auth and routing requirements via .npmrc.
3. If metadata lookup fails or no version satisfies constraints, npm throws a resolution error.

Prevention Tips

• Keep registry config and auth in .npmrc under version control (where appropriate).
• Pin versions (or use lockfiles) to avoid unexpected tag/range changes.
• Prefer a proxy/cache registry for CI stability.

Where This Can Be Triggered

// used by the ping and doctor commands
const npmFetch = require('npm-registry-fetch')
module.exports = async (flatOptions) => {
  const res = await npmFetch('/-/ping', { ...flatOptions, cache: false })
  return res.json().catch(() => ({}))
}