What Does Not Match This Runtime or Platform
npm returned EBADENGINE because the package declares Node.js or npm engine requirements that do not match the versions running your install.
Use a compatible runtime, platform, or published build
Switch to a supported Node version using your version manager or CI image, then reinstall dependencies.
If you control the package, only widen the engines field after confirming the code really supports the newer runtime.
If the failing dependency is outdated, upgrade to a version that supports your current Node or npm.
Why This Runtime or Platform Does Not Match
Usually this comes down to your current Node.js version is older or newer than the package supports, the package also constrains npm itself, and the running npm version is outside that range, or engine-strict or CI policy turns what would be a warning into a failing install.
Prove the Runtime and Published Build Now Line Up
node -v and npm -v now match the package's declared engines range, and re-run the original install and confirm EBADENGINE no longer appears.
Check runtime, platform, and index source
Print the current toolchain versions with node -v and npm -v, inspect the package requirements with npm view <pkg>@<version> engines or check the dependency package.json directly, and check whether strict enforcement is enabled with npm config get engine-strict.
Examples
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engineHow npm evaluates engine requirements
Packages can declare supported node and npm versions in the engines field of package.json. When your current runtime falls outside that range, npm warns or errors with EBADENGINE, especially when strict engine enforcement is enabled.
Prevent It From Coming Back
To prevent this, pin Node versions with .nvmrc, Volta, or CI setup so developers and runners use the same runtime, and check engines compatibility when upgrading Node or introducing new dependencies.