You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.
Hi - it doesn't appear that inline source maps are supported after glancing at tests. Inline source maps would be nice for dev testing over localhost when first setting up opbeat js. But more importantly, they would be helpful for staging environments limited to internal networks.
Thank you for your suggestion and for using opbeat-js :) , right now we rely solely on urls to provide sourcemap feature, but this might be something we consider in the future.
Have a good one,
Hamid
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi - it doesn't appear that inline source maps are supported after glancing at tests. Inline source maps would be nice for dev testing over localhost when first setting up opbeat js. But more importantly, they would be helpful for staging environments limited to internal networks.
Tried with inline source map -
Which it sent to opbeat as:
-- which it creates from https://github.com/opbeat/opbeat-js/blob/master/src/exceptions/context.js#L31
Seemed like an odd thing to send, so I also tried sending
data:application/json;base64...
but that 400s saying it expects full uri.The data is being sent to opbeat (likely not in a format server can handle), and then doesn't show stack trace in UI.
Thanks for any help!
Nick
The text was updated successfully, but these errors were encountered: