You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that Error.cause is somewhat standard, it's be great if the cause chain's stack traces would also be extracted when logging errors, sort of like the default .toString() of exceptions in Java.
This feature would be very handy. What's the progress about it? I'd like to implement it. Maybe integrate the cause into the field stack_trace. Would it be also a useful feature to print out the errors field of AggregateError?
Now that
Error.cause
is somewhat standard, it's be great if thecause
chain's stack traces would also be extracted when logging errors, sort of like the default .toString() of exceptions in Java.From what I could gather in the code, only
err.stack
is extracted.Looking at recent NodeJS docs, it does look like the internal formatter/inspector already handles the
cause
of an error when printing it.The text was updated successfully, but these errors were encountered: