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 was archived by the owner on Jan 12, 2024. It is now read-only.
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.
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.mapAlso, what IP does opbeat use to access the sourcemaps? Then we could limit sourcemaps to internal networks & opbeat.