Uh oh!
There was an error while loading. Please reload this page.
Add polyfill from polyfill.io - #174
Conversation
Note that we lock to the current default feature set (default-3.6). Future versions of create-react-app will want to update this version number, but we wouldn't want users to inadvertently get different polyfills.
gaearon
commented
Jul 25, 2016
Why would that be bad? They’re only adding, not removing stuff, right? |
ForbesLindesay
commented
Jul 25, 2016
Probably/Mostly. They haven't committed to never removing anything from the default set. Although they haven't done so yet, it would have been reasonable at one point for them to include You can see what they say about this under https://polyfill.io/v2/docs/features/#default-sets |
How about we use this set? https://cdn.polyfill.io/v2/polyfill.js?features=es6,fetch,Symbol&unknown=polyfill This seems like the most valuable stuff in React apps, and also protects against issues like #561 with |
gaearon
commented
Jul 25, 2016
It’s also more descriptive than |
gaearon
commented
Jul 25, 2016
Also worth checking: does their Promise polyfill swallow errors. |
JakeChampion
commented
Jul 25, 2016
I don't think you can solve uncaught rejections in userland (polyfills). |
gaearon
commented
Jul 25, 2016
Why not? It won’t be 100% accurate but we need to err on the side of less head scratching. Advanced Promise users who know what they’re doing with temporarily unhandled rejections will just include another polyfill. |
gaearon
commented
Jul 25, 2016
Also core-js does this. |
gaearon
commented
Jul 27, 2016
We went with embedded fetch and Promise polyfills for now so closing. |
Note that we lock to the current default feature set (default-3.6). Future versions of create-react-app will want to update this version number, but we wouldn't want users to inadvertently get different polyfills.
[closes#170]