7 ms·
Weird. Also just tried it with v8 and it doesn't behave like I remember and also not like certain descriptions that I can find online. I remember it because I w
by panzi 1y ago
Weird. Also just tried it with v8 and it doesn't behave like I remember and also not like certain descriptions that I can find online. I remember it because I was so extremely flabbergasted when I found out about this behavior and it made me go over all of my code replacing any Promise.all() with Promise.allSettled(). And it's not just me, this blog post talks about that behavior:
https://chrysanthos.xyz/article/dont-ever-use-promise-all/ https://chrysanthos.xyz/article/dont-ever-use-promise-all/
Maybe my bug was something else back then and I found a source claiming that behavior, so I changed my code and as a side effect my bug happened to go away coincidentally?
- kaoD 1y agoIt could be this: https://stackoverflow.com/questions/67789309/why-do-i-get-an-unhandled-promise-rejection-with-await-promise-all https://stackoverflow.com/questions/67789309/why-do-i-get-an... If you did something like: const p1 = makeP1(); const p2 = makeP2(); return await Promise.all([p1, p2]); It's possible that the heuristic didn't trigger?