Missing polyfill for Promise.allSettled
See original GitHub issueNow that Promise.allSettled
reached stage 4 of the specification process, would it make sense to add a polyfill for it to this project?
Or would you rather recommend to add a separate shim for it, something like es-shims/Promise.allSettled ? IMO that’s less convenient, but creating yet another implementation also sounds wrong.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Promise.allSettled in babel ES6 implementation - Stack Overflow
Currently I'm using q.allSettled as a workaround: import { allSettled } from 'q';. Is there something like that in babel polyfill? Alternatively, which ......
Read more >Polyfill for Promise.allSettled - Medium
allSettled () method returns a promise that resolves after all of the given promises have either resolved or rejected, with an array of...
Read more >An in depth explanation of Promise.all and comparison with ...
We will find out what exactly they do, what are the differences between them and even how we could create our own polyfill...
Read more >Promise API - The Modern JavaScript Tutorial
allSettled just waits for all promises to settle, regardless of the ... allSettled , it's easy to polyfill: ... If not, what am...
Read more >promise-all-settled-polyfill - npm package | Snyk
Learn more about promise-all-settled-polyfill: package health score, popularity, ... Looks like promise-all-settled-polyfill is missing a security policy.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
As a long-time user of this package, it never occured to me that it its features could be scoped to ES2015. I guess it’s because we’ve been using “ES6” as an inaccurate alias for “the time when we got new JavaScript features” for so long.
In any case, other packages I use have started to use
allSettled
, and they rarely make the destinction between ES levels. They just assumewindow.Promise
is supported with the current promise features. If this package would remain scoped to ES2015, I could no longer use it as an effective IE11 polyfill.I implemented this method https://github.com/WormGirl/core-promise