Question: Source mapping componentStack from error boundary in production
See original GitHub issueLately, I am trying to use error boundaries to tackle unexpected errors more properly. I am also logging most of the errors to the Sentry service. I am sending the componentStack
from componentDidMount
there as well, but since it’s minified, it feels fairly useless.
I am wondering what are my options if any. Since that output is pretty much just a string, the source mapping does not seem possible at any level.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:15
- Comments:29 (6 by maintainers)
Top Results From Across the Web
How to make Create React App Production Error Boundary ...
I found a solution to this using the library https://www.stacktracejs.com/. The method StackTrace.report() method will fetch the map and get ...
Read more >Error Boundaries - React
Error boundaries catch errors during rendering, in lifecycle methods, and in constructors of the whole tree below them.
Read more >React Error Boundary - Sentry Documentation
Learn how the React SDK exports an error boundary component that leverages ... Sentry with the above setup, but this won't occur in...
Read more >Handling JavaScript errors in React with error boundaries
Use error boundaries in React components to handle JavaScript errors, ... className="article-error"> <h3>There was a problem displaying the ...
Read more >React Error Handling And Reporting With Error Boundary And ...
The problem could happen in either of our three components above. When this happens, our beautifully crafted app comes crashing down like a ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh come on, I hate this little blue thing. Just because there is no viable answer yet, it shouldn’t be stale 😦 This is a real issue. Can someone please tell that robot it’s ok to keep it open?
Hi @iansu are the any updates on this issue? This is a significant for those of us who want to use error boundary to log errors.