Aggregate exception type vs. array of exceptions

[domenic]

The readme currently indicates that the rejection value would be an array of exceptions. Although this is not the worst thing, it definitely goes against prevailing practice to only throw exception types, and seems like it would play badly with lots of ecosystem code that assumes Error subclasses. For example, test frameworks or debugging tooling.

I have always hoped that the proposal for Promise.any would also introduce a new AggregateError type that contains a pointer to an array of exceptions.

[bakkot]

What would the message be?

[domenic]

Good question. Probably something generic, and unspecified, like all other message values?

[bakkot]

I guess what I mean is, what does new AggregateError(foo) do?

[ljharb]

i'd assume the constructor would take two arguments - message and an array of errors

[sindresorhus]

For reference, my p-any package throws an AggregateError (using aggregate-error).

[MattiasBuelens]

Another reason why I would prefer AggregateError: you get a separate stack trace for where the aggregate error was thrown (i.e. where you called Promise.any). 🙂