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 -
sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJzb3VyY2VzIjpbIndlYnBhY2s6L...
Which it sent to opbeat as:
http://localhost:8080/javascripts/clients/data:application/json;base64,eyJ2ZXJzaW9uIjozLCJzb3VyY2Vz...
-- 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
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