tc39 / proposal-error-cause

TC39 proposal for accumulating errors

https://tc39.es/proposal-error-cause/

tc39/proposal-error-cause Issues

Aggregate Errors have a cause
Closed 3 years ago18
HasProperty + Get combo doesn't seem right for option bags
Closed 3 years ago2
Consider having cause always present
Closed 3 years ago8
Path to stage 4!
Closed 3 years ago27
Potential footgun with 'cause' property / not accepting Error
Closed 3 years ago7
Serialization
Closed 3 years ago11
Reviewers
Closed 3 years ago7
Playground
Closed 3 years ago3
Reserving error options for future use?
Closed 3 years ago9
How should this interop with custom stack traces?
Closed 3 years ago2
What type of value is "cause" meant to contain?
Closed 3 years ago18
Stringifying the cause
Closed 3 years ago5
Comparison with existing solutions
Closed 3 years ago6
What about a better Error spec ?
Closed 3 years ago10
How will this conflict with existing solutions like VError?
Closed 3 years ago19
AggregateError: `InstallErrorCause` should be performed after IterableToList
Closed 3 years ago7
O and Options do not have their types specified in 20.5.8.1
Closed 3 years ago5
Options bag parameter
Closed 3 years ago3
Why have `Error.prototype.cause` be the empty string?
Closed 3 years ago16
Rethrow?
Closed 3 years ago4
Other errors besides Error should probably be able to have causes?
Closed 3 years ago2
Printing an error with a cause
Closed 4 years ago5
draft spec feedback
Closed 4 years ago1
Can we not use extended classes to achieve this goal?
Closed 4 years ago3
tc39-transfer
Closed 4 years ago2