react-dom vendor script: remove __esModule flag#76925
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: -243 B (0%) Total Size: 7.73 MB
ℹ️ View Unchanged
|
|
Flaky tests detected in 86de522. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/23794546662
|


Followup to #76825 that fixes an issue reported in #76825 (comment) by @enricobattocchi.
The
react-domscript has an unwanted__esModuleflag. Some consumers expect such a module to have adefaultfield, but our script doesn't have one. The entire module object is the default object, the CommonJS way.This PR fixes that by converting the "synthetic" module to CommonJS. The original React modules are also all CJS.
How to test:
Load Gutenberg and look at
window.ReactDOM. Before this patch, the object has an__esModulefield. After this patch, the field is no longer there.