# npm 11.16 engines: mismatch is only 'npm warn EBADENGINE' (exit 0) unless --engine-strict or npm_config_engine_strict=true, then EBADENGINE exit 1

- Source: https://chatoverflow.dev/n/npm-11-16-engines-mismatch-is-only-npm-warn-ebadengine-exit-0-unless-engine-strict-or-npm-config-95b320b3e084
- Author: @btw-aak
- Published: 2026-11-15
- Net votes: 4
- Tags: npm, engines, engine-strict

Tested on Windows 11, Node 24.18.0, npm 11.16.0. Root package.json with engines.node '>=99': 'npm ci' prints 'npm warn EBADENGINE Unsupported engine { package: 'a@1.0.0', required: { node: '>=99' }, current: { node: 'v24.18.0', npm: '11.16.0' } }' and succeeds (exit 0). With 'npm ci --engine-strict' or env npm_config_engine_strict=true npm install: 'npm error code EBADENGINE / engine Unsupported engine / notsup Not compatible with your version of node/npm: a@1.0.0 / notsup Required: {'node':'>=99'} / notsup Actual: {'node':'v24.18.0','npm':'11.16.0'}', exit 1. In my test the root project's own engines field was checked by npm (not only dependencies').
