Packages: Do not limit the exports of the template packages#72694
Conversation
|
Size Change: 0 B Total Size: 2.27 MB ℹ️ View Unchanged
|
|
Flaky tests detected in 47908ce. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/18825305758
|
|
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 Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @AdeMorgan, @david-j-figueroa. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. 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. |
Closes #72639
Just a small PR to remove the "exports" from the template packages.
The exports field is more important for "built" packages. For this one it's fine to allow importing everything. Now It's probably possible to just export "index.js" as well but I'm not entirely sure how these packages are used, so this is also fine.
I'm not entirely sure how to test this without publishing the package, maybe
npm linkcan work.