-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Dependency extraction: Map to regenerator-runtime
instead of wp-polyfill
#63091
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: 1.75 MB ℹ️ View Unchanged
|
This changes make sense to me. Should we backport this one into 6.6? |
Ya let‘s do that so its published earlier 👍 |
I just cherry-picked this PR to the wp/6.6 branch to get it included in the next release: f66826e |
What?
This is a follow-up to https://core.trac.wordpress.org/ticket/60962 in WP 6.6, where
regenerator-runtime
was removed as a dependency fromwp-polyfill
. Now it needs to be added explicitly if still needed.Why?
Via #63009 I realized that
@WordPress/dependency-extraction-webpack-plugin
still points towp-polyfill
though when using regenerator (which shouldn't happen when targeting newer browsers anyway).How?
Externalizes regenerator to
regenerator-runtime
directly instead ofwp-polyfill
Testing Instructions
If using generators in a script and targeting older browsers such as IE 11,
regenerator-runtime
would be added as a dependency instead ofwpo-polyfill
.Testing Instructions for Keyboard
N/A
Screenshots or screencast
N/A