I have an issue with the new React Error Boundaries and source maps.
Sometimes errors produced by Error Boundaries don’t have a stack trace, however the info object (second parameter of componentDidCatch contains a componentStack field with a stack trace like string. I’m sending that stack trace to Sentry in the extra field, but of course, no source maps are applied to it so it is kind of useless.
I wonder if it would make sense for Sentry to provide a fields where you can manually add a stack trace as a string? That would solve my issue and potentially similar issues where stack traces are not obtained the standard way.