Repository navigation
Feat: Build/Test Tools: Upgrade Node.js to 24.x (24.18) and npm to 11.x - #1067
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #1067 +/- ##
==========================================
Coverage 80.87% 80.87%
Complexity 2998 2998
==========================================
Files 124 124
Lines 11987 11987
==========================================
Hits 9695 9695
Misses 2292 2292
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
What?
Closes #1066
Upgrades the plugin's Node.js/npm tooling from Node 22 / npm 10 to Node 24.18 / npm 11.16, matching WordPress Core and Gutenberg.
Why?
WordPress Core (r63539) and Gutenberg (#82370) now require Node
>=24.18.0and npm>=11.16.0. Using the same versions keeps local development and CI consistent across the projects.How?
.nvmrc:22→24.18. All workflows readnode-version-file: '.nvmrc', so no workflow changes are needed.package.json:engines.node→>=24.18.0,engines.npm→>=11.16.0.package-lock.json: regenerated with npm 11 (--package-lock-only). No resolved versions changed. The diff is the rootenginesvalues, npm 11 flag cleanup (dev→devOptional), and a few entries npm 11 dropped because they were unused or optional-only. That includes two nesteddate-fns@4.4.0copies under@base-ui/react, wheredate-fnsis only an optional peer dependency.CONTRIBUTING.mdandtests/e2e/README.mdnow list the new versions.Note
.npmrchasengine-strict = true, sonpm ci/npm iwill fail on Node < 24.18 or npm < 11.16. Runnvm install && nvm usebefore installing.Use of AI Tools
AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Auditing Node version references, making the version changes, and verifying the build. I reviewed all changes.
Testing Instructions
nvm install && nvm useand confirmnode -vis 24.18.x andnpm -vis ≥ 11.16.npm cishould complete with noEBADENGINEerrors.npm run build,npm run lint:js, andnpm run typecheckshould all pass.npm run wp-env:test start && npm run test:e2eshould pass.Changelog Entry