-
Notifications
You must be signed in to change notification settings - Fork 286
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
es6-promise is not a safe polyfill to recommend in your readme #111
Comments
I came from stefanpenner/es6-promise#70 (comment) Maybe you could give Promise lib yaku a try. Features
|
Yaku looks excellent, and ticks all my personal boxes, thank you! I love the fact it's small and has passing test coverage too, seems like a good fit for alternative polyfill recommendation here! I've been trying to pin this down even more, because when I actually hit it I felt it was way worse than I've actually demonstrated so far. And I remembered that even when you To me this is the most concrete example, where the developer is absolutely doing all the right things, and the error is STILL swallowed: http://requirebin.com/?gist=9c59be0170fa7691a534705daf6b765d And (now using Yaku as alternative), here's how you do it right: http://requirebin.com/?gist=8e1d11f8754e58afd271a994760bb0c4 |
If you have any problem with Yaku, please feel free to issue me. The project is quite active to user feedbacks now. |
Sad story.
|
I would recommend looking at promise-polyfill. I tested a bunch of polyfills and it's the smallest and I don't think it has that footgun. |
This repo no longer recommends any polyfill. |
es6-promise's strict spec handling of uncaught exceptions (by not doing so at all) is a footgun. I don't feel like it should be the default recommendation of polyfill, and personally is the reason I've kept my team away from
fetch()
for months. Here are examples why:Bluebird, however does the right thing:
I'm not saying Bluebird should be what you suggest instead, as I haven't dug into relative sizes/support/practicalities of that. I just feel that recommending people use es6-promise is going to cause a lot of people pain.
The text was updated successfully, but these errors were encountered: