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
Debug ID's are globally unique identifiers that allow users and software to bidirectionally link sourcemaps to generated files without needing to rely on file names or other external information.
We've had a lot of success at Sentry implementing this for our error monitoring product (unminifying production JavaScript stacktraces), and we think it would be good for the community to also move forward with this.
This comes in a couple of steps:
Productionize https://github.com/getsentry/javascript-debug-ids and release packages for standalone debug id implementations. This includes bundler plugins/cli tooling to generate debug ids and a polyfill that allows you to find a debug id from a loaded JavaScript file.
Advocate to various JavaScript tooling to adopt debug ids based on the work we've done in this repo.
Push forward a JavaScript API for debug ids in tc39.
Push forward debug ids to become part of the official sourcemaps spec.
The text was updated successfully, but these errors were encountered:
https://getsentry.github.io/debugids/
Debug ID's are globally unique identifiers that allow users and software to bidirectionally link sourcemaps to generated files without needing to rely on file names or other external information.
We've had a lot of success at Sentry implementing this for our error monitoring product (unminifying production JavaScript stacktraces), and we think it would be good for the community to also move forward with this.
This comes in a couple of steps:
The text was updated successfully, but these errors were encountered: