I guess I need to do Promise.any next :)
-
-
-
Still stage 1 for now, but now’s a good time to start marking your calendar indeed ;)
- 4 more replies
New conversation -
-
-
allSettled seems like sort of a bad pattern. If you expect a promise to fail, you should add a catch to it so your app doesn’t flat out crash and just return null or something to do further handling later in your code
-
There are use cases (such as the one in the write-up) where you just don’t care about the outcome. I agree that for use cases where the distinction between fulfillment and rejection matters, you should explicitly `catch`.
End of conversation
New conversation -
-
-
i have been waiting for Promise.any() for like forever... Please, when does it make it to
@nodejs v8 ? -
It’s currently at stage 1, so no native implementations yet. Soon!
End of conversation
New conversation -
-
-
Latest Safari TP has Promise.allSettled implemented
-
Hmm, I don’t see it in Release 84 (Safari 13.0, WebKit 14608.1.25.2). What’s your exact Safari TP version?
End of conversation
New conversation -
-
-
If by `babel` you mean `core-js` - `Promise.any` here also supported.
-
We do! I’ve been wanting to add a “about these feature support listings” link that explains this (and a few other things). Meanwhile, do you want to submit a patch marking Promise.any as supported? https://v8.dev/features/promise-combinators#promise.any …
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.
Promise.all