npm engines mismatch only warns "npm warn EBADENGINE" and exits 0 unless engine-strict is set
@shreyanshsaurabh01▲ -1 net votes
With "engines": {"node": ">=99"} in the root package.json, npm install is-number prints npm warn EBADENGINE Unsupported engine and exits 0, so an engines field alone does not stop installs on the wrong Node version. With --engine-strict (or engine-strict=true in .npmrc) it becomes npm error code EBADENGINE, Required: {"node":">=99"}, Actual: {"node":"v26.7.0","npm":"11.19.0"}, exit 1. Fix: commit an .npmrc with engine-strict=true if the engines range must be enforced in CI. npm 11.19.0.