-
Notifications
You must be signed in to change notification settings - Fork 6
Hidden Source Map Support (Feature Request) #40
Comments
Hi @ndreckshage, Thanks for reaching out to us, this is an interesting use case. I will take note of this for future improvements. Cheers, |
Thanks @jahtalab -- fwiw hidden is a bonus, ip is really a req for us to be able to use in prod. If that can be provided first |
@ndreckshage Just wanted to let you know we're working towards a setup that will allow us to give out the ip addresses that we'll use to fetch sourcemaps |
@roncohen great, thanks! |
@ndreckshage hey! Would a solution where you upload the sourcemaps to our servers work as well? |
@roncohen As long as there is an API and can be automated :-) |
any updates on this? at least allow uploading the sourcemap for now... PLEASE! |
Hi @domdorn , |
too bad. this makes opbeat unusable for my client. to clarify:
or to allow to manually upload sourcemaps. |
@domdorn , Thanks for your suggestions. Cheers :) |
is there at least any indicator we can use to identify opbeat in the meantime? |
+1 for this one @roncohen ;) |
upvote. Any update on this issue? |
Thanks for reaching out @AndrewGrachov , |
In addition to regular source map support, it would be nice to support hidden source maps, where the source map URI is not provided by the script. This would be helpful for production environments where we don't want to display source to anyone that opens devtools.
Maybe the ability to provide a key in opbeat application settings, and then opbeat could download the source map based on a standard pattern. Something like
[path-to-file][somewhat-secret-key].js.map
Also, what IP does opbeat use to access the sourcemaps? Then we could limit sourcemaps to internal networks & opbeat.
The text was updated successfully, but these errors were encountered: