One of many large themes of the net as of late is concurrency, which ends up in carrying out duties asynchronously. In doing so, the potential of a number of errors can happen. As a substitute of offering a generic error, optimally you’d present a wealth of error data. TheAggregateError error lets builders throw a number of errors inside one single Error. Let’s examine the way it works.

To throw a single error that represents a number of errors, let’s make use of AggregateError:

const error = new AggregateError([
  new Error('ERROR_11112'),
  new TypeError('First name must be a string'),
  new RangeError('Transaction value must be at least 1'),
  new URIError('User profile link must be https'),
], 'Transaction can't be processed')

Throwing an AggregateError will get you the next data:

error instanceof AggregateError // true
error.title // 'AggregateError'
error.message // 'Transaction can't be processed'
error.errors // The array of errors

The AggregateError is extremely helpful when validating a number of units of information; as a substitute of throwing one error at a time, grouping them into one is right! AggregateError could be actually helpful in a Promise.any state of affairs. Communicative, information-rich errors FTW!