p-all

Summary improve one README sentence by tightening the wording around concurrency limits Related issue N/A (trivial docs wording fix) Guideline alignment CONTRIBUTING: none found in the repo root or .github on main PR template: none found in the repo root or .github on main Validation Not run (docs-only change)

Unsure if this is a typescript problem, or something related to the definition of p-all's types It seems that if the task passed to uses internally, the api fails to infer the proper type of the result, unless the task is defined as async. I am using in a complex scenario, but a simplified code in which I was able to reproduce the bug is: If I hover on visual studio code, is inferred as The proper inference should be Workaround If the task is defined as , the type is inferred correctly The type is now correctly inferred If I use an intermediate variable, it also works (without async) if I hover on VS code: type is correctly inferred Test that should pass

Hello, I'm using this library to quickly replace calls that are currently to avoid an issue with orphaned promises after one fails. However this throws an on which changes the semantics. It would be nice if it could keep the exception semantics, but still wait. I understand I can just replace things with or some such, although that also changes the semantics since the order of failure is lost.