Repository navigation
Redo "Framework: Update Node.js to v24 LTS and npm to v11" - #82370
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueComment |
🤖 PR meta 🤖📦 Bundle sizeSize Change: 0 B Total Size: 8 MB
⚡ PerformanceShow the resultsClient side metrics exclude the server response time. front-end-block-theme
front-end-classic-theme
media-processing
media-upload
post-editor
site-editor
|
4afe20c to
fbd8563
Compare
|
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. |
Node.js was updated to v24 LTS in #82370, so align the type definitions with the runtime the repository builds and tests against. Bumps every workspace's `@types/node` devDependency to ^24.13.3 and relaxes the `@wordpress/e2e-test-utils-playwright` peerDependency to ^24.0.0.
Node.js was updated to v24 LTS in #82370, so align the type definitions with the runtime the repository builds and tests against. Bumps every workspace's `@types/node` devDependency to ^24.13.3 and relaxes the `@wordpress/e2e-test-utils-playwright` peerDependency to ^24.0.0.
* Framework: Update @types/node to v24 Node.js was updated to v24 LTS in #82370, so align the type definitions with the runtime the repository builds and tests against. Bumps every workspace's `@types/node` devDependency to ^24.13.3 and relaxes the `@wordpress/e2e-test-utils-playwright` peerDependency to ^24.0.0. * Add the PR reference to the changelog entry * Widen the e2e-test-utils-playwright `@types/node` peer range to >=20 The package's own `engines.node` is still >=18.12.0 and its public types only touch long-stable Node APIs, so pinning the peer to a single major would break consumers on older type definitions for no gain. Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
What?
We tried to upgrade to Node 24 in #80395 but had to revert it in #82355 due to some build failures in
wordpress-develop. This PR makes the change ready to be redone.Why?
See #80395
How?
See #80395
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast
Use of AI Tools