-
Notifications
You must be signed in to change notification settings - Fork 170
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
Source map support to trace production errors #219
Comments
I' also very curious if this is possible @OsamaAbbas - it will be of a great help for debugging issues, specially with sentry indeed. |
The first comment of this issue is clear that the error comes from That being said, I remember that I could implement source map generation previously (two years ago or so). I don't remember how exactly I did it though! It was probably something like this: we know that the dummy code is just a string or a series of empty characters, with no |
I found the old comment with some details on how to implement source maps (from 2020). |
Source maps would be very cool! Though we should certainly default to disabling them… and explaining to people clearly why they might want to keep them disabled. |
1 similar comment
Source maps would be very cool! Though we should certainly default to disabling them… and explaining to people clearly why they might want to keep them disabled. |
I am using Sentry for error monitoring and I want to get a proper stacktrace to fix production issues.
With bytenode enabled, I am unable to generate source maps.
Sentry throws the below exception
(vite:bytecode plugin) Sourcemap is likely to be incorrect: a plugin (vite:bytecode) was used to transform files, but didn't generate a sourcemap for the transformation. Consult the plugin documentation for help
Any solution to generate source map? Or this is never possible?
The text was updated successfully, but these errors were encountered: