Repository navigation
Build: Remove patch-package - #83982
Conversation
No patches remain and patch-package does not work with install-strategy=linked.
🤖 PR meta 🤖🎉 PropsIf 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. Updated as activity occurs, without notifying anyone named here. Add the 📦 Bundle sizeSize Change: 0 B Total Size: 8.25 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
🏁 Flaky testsSome tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information. should cut and paste individual blocks with collapsed selection in
|
|
Nice! 🎉 I've long awaited this day 😄 Hopefully we can get rid of the |
Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org> Co-authored-by: ciampo <mciampini@git.wordpress.org>
What?
Follow up to #83847 and #83132
Removes
patch-packagefrom the root dev dependencies and thepostinstallscript, along with the emptypatches/directory.Why?
The last patch was removed in #83132, so
patch-packagehas had nothing to apply. Since #83847 switched toinstall-strategy=linked, it would not work anyway: it patches the hoistednode_modules/<pkg>path, which no longer holds the real package.How?
patch-package &&prefix frompostinstallin package.json.patches/README.md.patches/**from the npm cache key in .github/setup-npm/action.yml and the stale comment in.github/setup-node/action.yml.The patch-package example in the iframe migration guide stays, since it targets third-party block authors.
Testing Instructions
npm installcompletes andpostinstallonly runsagents:setup.Use of AI Tools
Authored with Claude Code, reviewed by me.