Keeping npm up to date in Node.js
Open
@reggi is already working on this.
Since Jul 31, 2026.
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Keeping npm up to date in Node.js
Hi Node.js team! I (@reggi) opened npm update PRs for the supported Node.js branches.
The Node.js branches are currently out of sync:
| Node.js | Status | Bundled npm | Latest release in that npm major |
|---|---|---|---|
| 26 | Current | 11.17.0 | 11.19.0 |
| 25 | EOL | 11.12.1 | 11.19.0 |
| 24 | Active LTS | 11.16.0 | 11.19.0 |
| 23 | EOL | 10.9.2 | 10.9.9 |
| 22 | Maintenance LTS | 10.9.8 | 10.9.9 |
| 21 | EOL | 10.5.0 | 10.9.9 |
| 20 | EOL | 10.8.2 | 10.9.9 |
| 19 | EOL | 9.6.3 | 9.9.4 |
| 18 | EOL | 10.8.2 | 10.9.9 |
We opened these PRs to update the supported branches:
- npm 12.0.2 → Node.js
main: https://github.com/nodejs/node/pull/64882 - npm 11.19.0 → Node.js
v26.x-staging: https://github.com/nodejs/node/pull/64883 - npm 10.9.9 → Node.js
v22.x-staging: https://github.com/nodejs/node/pull/64884 - npm 11.19.0 → Node.js
v24.x-staging: https://github.com/nodejs/node/pull/64885
These are the commands I ran:
gh workflow run create-node-pr.yml -R npm/cli -f spec=latest -f branch=main
gh workflow run create-node-pr.yml -R npm/cli -f spec=next-11 -f branch=26
gh workflow run create-node-pr.yml -R npm/cli -f spec=next-11 -f branch=24
gh workflow run create-node-pr.yml -R npm/cli -f spec=next-10 -f branch=22
I did not create PRs against EOL branches.
- Should we update those branches as well?
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.
Assessment
This issue has not been assessed yet.