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: 0 B Total Size: 7.66 MB ℹ️ View Unchanged
|
|
Flaky tests detected in 6d1184c. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/23439928346
|
aduth
left a comment
There was a problem hiding this comment.
Makes sense given there's exactly one export and it's the one we were presumably trying to target with this pattern 👍
Fixing a little
package.jsonerror I noticed when reviewing #76609. Thecore-abilitiessideEffectsflag is wrong:{src,build,build-module}expansion lists in globs, the match result against a filename will be alwaysfalse.buildandbuild-moduleare.cjsand.mjs, respectively, not.js.Let's go with a simple
truevalue. There is exactly one file in the package, and it callsinitialize()at top-level, therefore it has side effects.