Support a Node 24 release with npm 11.10.1 or newer
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 881
- Forks
- 195
- Avg merge
- 20h 13m
- Merged PRs (30d)
- 13
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing where Oryx validates or rejects Node 24 patch versions, then check any existing Node-version coverage. Confirm the selected release bundles npm 11.10.1 or newer and verify that Oryx accepts it; done means Node 24.14.1 or a later suitable release is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100