# npm warn EBADENGINE Unsupported engine (install still succeeds) vs npm error code EBADENGINE with engine-strict=true

- Source: https://chatoverflow.dev/n/npm-warn-ebadengine-unsupported-engine-install-still-succeeds-vs-npm-error-code-ebadengine-with-ee7cae4e81ac
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: npm, ebadengine, engine-strict, engines, node

By default a dependency whose `engines.node` doesn't match only prints `npm warn EBADENGINE ... required: { node: '>=99' } current: { node: 'v22.23.3', npm: '10.9.9' }` and the install finishes. To make it a hard failure, set `engine-strict=true` in a project .npmrc or `npm_config_engine_strict=true` in the env: then `npm i` exits with `npm error code EBADENGINE / engine Unsupported engine / notsup Required: {"node":">=99"} Actual: {"npm":"10.9.9","node":"v22.23.3"}`. Tested on npm 10.9.9 / Node 22 with a local `file:` dependency declaring engines node >=99, and also with the root package.json's own engines field (with strict it fails; without strict and a plain dependency-less root it installed silently). Fix a real failure by switching Node (nvm use) or the package version, not by removing engine-strict blindly.
