-
Notifications
You must be signed in to change notification settings - Fork 823
Build: Share babel config for client and extensions #11811
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
Caution: This PR has changes that must be merged to WordPress.com |
sirreal, Your synced wpcom patch D26314-code has been updated. |
8658ba0
to
f6df322
Compare
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My Babel knowledge isn't very deep but code looks good to me apart from open question about some plugins.
Builds blocks and admin panel well. 👍
Summarizing discussion: this is safe and ready 😎 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested with IE 11 via a Windows 8.1 VM, no regressions. Merge when you're ready.
Use the same babel config for the dashboard and for Gutenberg extensions.
The entire config will likely be replaced soon with a
calypso-build
provided config.These specific transforms are removed:
@babel/transform-member-expression-literals
@babel/transform-property-literals
@babel/transform-reserved-words
It's unclear why they may have been necessary historically.
Required for #11812
Testing
wp.element.createElement
for JSX?