Problem
The latest Node 24 version currently accepted by our Azure Static Web Apps Oryx build is Node 24.13.0, which bundles npm 11.6.2.
npm 11.6.2 can produce a package-lock.json with npm install that is subsequently rejected by npm ci as out of sync. We confirmed this is not caused by different npm versions between lockfile generation and CI: both environments use npm 11.6.2.
Related npm reports:
The relevant npm fix is available from npm 11.10.1 onwards. Node 24.14.1, for example, bundles npm 11.11.0, but Oryx currently rejects that Node version as unsupported.
Requested change
Please add support for a Node 24 patch release that bundles npm 11.10.1 or newer, such as Node 24.14.1 or later.
Until then, our CI workaround is to use npm install instead of npm ci, which means we temporarily lose clean, lockfile-only dependency installation.
Related Oryx issue
Problem
The latest Node 24 version currently accepted by our Azure Static Web Apps Oryx build is Node
24.13.0, which bundles npm11.6.2.npm
11.6.2can produce apackage-lock.jsonwithnpm installthat is subsequently rejected bynpm cias out of sync. We confirmed this is not caused by different npm versions between lockfile generation and CI: both environments use npm11.6.2.Related npm reports:
npm cifails with "package.json and package-lock.json are out of sync" when new patch versions are published npm/cli#8693npm cifails becausenpm installproduces an out-of-sync lockfile (regression since v7.0.9) npm/cli#8726The relevant npm fix is available from npm
11.10.1onwards. Node24.14.1, for example, bundles npm11.11.0, but Oryx currently rejects that Node version as unsupported.Requested change
Please add support for a Node 24 patch release that bundles npm
11.10.1or newer, such as Node24.14.1or later.Until then, our CI workaround is to use
npm installinstead ofnpm ci, which means we temporarily lose clean, lockfile-only dependency installation.Related Oryx issue