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 IDs are unique IDs generated from a deterministic hash of the source code which are then injected/included in both source and sourcemap. They can be used to easily identify the correct sourcemaps in production.
I've recently added support for injecting debug IDs to webpack, Rollup, and Rolldown and wanted to get them working in esbuild too but I don't really know Go yet!
The text was updated successfully, but these errors were encountered:
Thanks for the heads up. However, it looks like it's only at stage 2, which is defined as "There is a very high risk of incompatible changes, so they should not be exposed to production users." So it sounds like it's not ready to implement yet.
It's worth noting that the proposal is in two parts:
Debug ID in magic comment in source linked with debugId key in sourcemap json
JavaScript API to allow access to debug ID magic comment at runtime
While the runtime JavaScript API still has a high risk of changes, the source comments and linked with sourcemap key are not likely to change and are already used in millions of production deployments and have been implemented in other bundlers.
Debug IDs are detailed in the TC39 proposal.
Debug IDs are unique IDs generated from a deterministic hash of the source code which are then injected/included in both source and sourcemap. They can be used to easily identify the correct sourcemaps in production.
I've recently added support for injecting debug IDs to webpack, Rollup, and Rolldown and wanted to get them working in esbuild too but I don't really know Go yet!
The text was updated successfully, but these errors were encountered: