New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Javascript source maps #1239
Comments
It isn't, but I really wish it was. I haven't looked too deeply into the way airbrake does this, but I think this could be implemented without any errbit changes. If I had the time, I'd like to experiment with a client-side JavaScript package that can take a stacktrace from a bunch of minified javascript, download the source maps for the files referenced, and create a new, more legible stack trace from that. Sending it to Errbit from that point would be a simple matter. |
@stevecrozz - right, that might be true. I've made some research and found out https://www.stacktracejs.com/ which might be helpful here, I'll play around and let you know 👍 |
@kbiedrzycki any interesting developments? :) |
It would probably be better to make the backend download sources & maps and follow the airbrake-js docs. |
At first i have to say many thanks for your service |
Errbit is an awesome open source project! Really hope errbit can support source maps to trace down React errors! |
@yoonwaiyan @miladmeidanshahi @jsg2021 @rud this is on my personal roadmap, I would like to add JS source maps support here in errbit (similar way how rollbar get's them). I'll keep you updated. |
Here's my implementation #1480 |
Any updates on this? 👀 |
It's more like a question than issue - is errbit capable of handling javascript source maps? Now, when I am reviewing errors handled by errbit I can see minified backtrace. I see that Airbrake api can handle source maps, how it looks like with errbit support to handle sourcemaps?
The text was updated successfully, but these errors were encountered: