Description
We're using the provided React error boundary to capture app wide errors. This is working, but the included react.componentStack metadata doesn't take advantage of our uploaded source maps and still shows up as minified. This makes this information fairly useless, it would be nice to have proper source mapping in this section like we do in the stacktrace tab
Describe the solution you'd like
Provide some sort of mechanism for metadata that can allow us to pass a data format that can, at a minimum, take advantage of uploaded source maps, and ideally, be rendered nicely like the stacktrace tab. Also, update the React error boundary to use this new mechanism out of the box for react.componentStack metadata.
Describe alternatives you've considered
No alternative features. One possible workaround on our end is doing this mapping manually. We have access to our own source maps on our server, so we could expose a sort of bugsnag proxy API that can special case handle react.componentStack by reading on disk source maps and string substituting the minified names/file/row/column for the actual component name/file/row/column.
Description
We're using the provided React error boundary to capture app wide errors. This is working, but the included
react.componentStackmetadata doesn't take advantage of our uploaded source maps and still shows up as minified. This makes this information fairly useless, it would be nice to have proper source mapping in this section like we do in thestacktracetabDescribe the solution you'd like
Provide some sort of mechanism for
metadatathat can allow us to pass a data format that can, at a minimum, take advantage of uploaded source maps, and ideally, be rendered nicely like thestacktracetab. Also, update the React error boundary to use this new mechanism out of the box forreact.componentStackmetadata.Describe alternatives you've considered
No alternative features. One possible workaround on our end is doing this mapping manually. We have access to our own source maps on our server, so we could expose a sort of bugsnag proxy API that can special case handle
react.componentStackby reading on disk source maps and string substituting the minified names/file/row/column for the actual component name/file/row/column.