-
Notifications
You must be signed in to change notification settings - Fork 4.6k
wp-ui: add legacy export fields to package.json #73850
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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: 2.57 MB ℹ️ View Unchanged
|
Add the legacy
main,module,typesfields topackage.json. OurtranspilePackagebuild script relies on presence ofpackageJson.mainandpackageJson.module. Without this, thebuildandbuild-modulefolders are not built and the published package is broken:https://app.unpkg.com/@wordpress/[email protected]
The
typesfield is not strictly necessary, but I'm adding it for consistency with other packages.After we merge this, let's publish a
nextversion of the packages to NPM ASAP.