Description
Bug Report
- I would like to work on a fix!
Current behavior
The Usage Guide Overview talks about installing @babel/polyfill
, which is now deprecated.
Expected behavior
The guide would provide instructions for the more contemporary way of providing polyfills with core-js
and regenerator-runtime
.
Environment
Web
Possible Solution
Could be some pretty easy docs updates, would be happy to write them if I get can a 👍 from someone on the team.
Activity
babel-bot commentedon Nov 25, 2020
Hey @AndrewSouthpaw! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.
If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite."
nicolo-ribaudo commentedon Nov 26, 2020
Yes please! 👍
If you need any help feel free to ask.
aavmurphy commentedon Feb 17, 2021
This is a really important fix.
[For web js]
'transpiles' work well, but I was unable to figure out how
core-js
andregenerator-runtime
worked, or if they were needed.With the
debug
option set, I get auseBuiltIns not set
warning messsage (but not which input-js/polyfills caused it).If I set
useBuiltIns
, I get lots of duplicated 'import' statements in the output js (is import safe web js?)<script src=file>
I'm obviously missing something.
This might be a separate issue, but some debug message like "array.entries() needs a 50K polyfill because of safari 10.x" would be useful. Use it 100x, OK, use it once, it might be simpler to use an alternative.