Revert "wp-build: Replace getter-based exports with data properties"#78917
Conversation
|
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. |
|
Size Change: -2.37 kB (-0.03%) Total Size: 8.21 MB 📦 View Changed
ℹ️ View Unchanged
|
Judging by the issue description, I'm understanding the issue not to be that this is |
aduth
left a comment
There was a problem hiding this comment.
Tested locally as described above, and verified that the changes are a clean revert of the original code (not including the changelog).
Good point! I updated the PR description! Thanks! |
What?
Follow up to #78303.
This PR reverts the patch introduced in #78303, which replaced getter-based exports in
@wordpress/buildwith data properties.Why?
Gutenberg 23.0 introduced regressions tracked in #78697. For additional context, see:
Reverting the change restores the previous behavior while we prepare a patch release. After the patch release is shipped, we can revisit the approach from #78303 and explore an alternative solution.
How?
This reverts the changes from #78303 in
packages/wp-build/lib/build.mjs, restoring the previous getter-based export behavior.Testing Instructions
npm run build.window.wp.isShallowEqual.__esModuleisn't undefined.Testing Instructions for Keyboard
This PR does not change the user interface.
Screenshots or screencast
Not applicable.