Skip to content
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.

Inline Source Map Support (Feature Request) #39

Open
ndreckshage opened this issue Feb 2, 2016 · 1 comment
Open

Inline Source Map Support (Feature Request) #39

ndreckshage opened this issue Feb 2, 2016 · 1 comment

Comments

@ndreckshage
Copy link

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

@hmdhk
Copy link
Contributor

hmdhk commented Feb 2, 2016

@ndreckshage ,

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants