Question: Source mapping componentStack from error boundary in production

[danielkcz]

Lately, 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.

[iansu]

You can upload your sourcemaps to Sentry. That might help in this situation.

[danielkcz]

@iansu That surely won't work because the componentStack is just a string, there is no structured information to feed source mapping mechanism. Have a look at this example (used to showcase different issue).

https://codesandbox.io/s/zw500lpm2p

Source map upload definitely doesn't help. I have it uploaded, my stack trace is decoded properly, but componentStack is not.

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[danielkcz]

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?

[jeremygottfried]

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.

[iansu]

There is no update on this. As far as I know no one is working on it.

[Tonyce]

I have the same problem。Since React have given this component idea，I also expect a way.

[robertvansteen]

Duplicate of #3753