-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
babel/polyfill deprecation notice implies the necessity to include core-js/stable even when useBuiltIns = usage #2332
Comments
Hey @dmitriyshashkin! We really appreciate you taking the time to report an issue. The collaborators If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack |
Update the documentation to state first how to poliyfill with core-js. Solves babel#2240, babel#2163, babel#2332 and babel#2006
* Update usage.md Updated usage.md to not recommend the use of `[@babel/polyfill](https://babeljs.io/docs/en/babel-polyfill)`, which is deprecated. Solves #2171 * Update usage.md to include usage of core-js polyfill Update the documentation to state first how to poliyfill with core-js. Solves #2240, #2163, #2332 and #2006 * fix typo in previous commit Fix in usage.md where I was referring(linking) to where deprecated was stated * update usage.md to describe regenerator-runtime polyfills I updated this doc to describe the use of regenerator-runtime polyfills and when to use them.
This guide here says that instead of using https://babeljs.io/docs/en/usage#polyfill package one should include directly "core-js/stable".
But as I understand if I'm using
"useBuiltIns": "usage"
I should not include "core-js/stable" directly.Yes, the documentation states that if I'm using @babel/preset-env with useBuiltIns = usage I should not include @babel/polyfill But I was sure it only relates to @babel/polyfill import which is now deprecated.
The text was updated successfully, but these errors were encountered: