blakeembrey / blakeembrey/make-error-cause

Use in Chrome dev tools doesn't show full stacks

Open
#38 4 comments 1 reaction 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
69
Forks
8
PR merge metrics
No merged PRs in 30d

Description

I've been using make-error-cause in my back end and it works great. Tried it today in my front end, but `console.error(err)` mangles the stack traces for the causes (because Chrome dev tools doesn't show newlines perhaps?)

![image](https://user-images.githubusercontent.com/139975/79270475-3e005b80-7e6c-11ea-8a2a-1386d2509985.png)

I also tried `console.error(fullStack(err))` and that has the separator text, but omits the stacks entirely (except console.error itself shows the stack of the last, outermost, error when twirled open):
![image](https://user-images.githubusercontent.com/139975/79270744-a7806a00-7e6c-11ea-82f8-fd03621f38a0.png)

Is there anything I can do to get nice stack traces for the earlier/inner errors in dev tools?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.