Problem Statement
In the most recent release of Angular v22.1.0, Angular is generating Debug IDs:
https://github.com/angular/angular-cli/releases#release-v22.1.0
angular/angular-cli@0c18dc0
This helps to properly work with Angular's built-in subresource integrity hash generation.
Before Sentry would have changed the files after they have been generated by Angular, breaking the integrity hashes of the files.
Solution Brainstorm
Does this need an update of those two Angular documentation pages?
https://github.com/getsentry/sentry-docs/blob/master/docs/platforms/javascript/common/sourcemaps/uploading/angular-nx.mdx
https://github.com/getsentry/sentry-docs/blob/master/docs/platforms/javascript/common/sourcemaps/uploading/angular-webpack.mdx
We've been using nx with the Sentry CLI, so we simply stopped using the CLI, however, is there any option to disable the debug ID generation for Angular?
Problem Statement
In the most recent release of Angular
v22.1.0, Angular is generating Debug IDs:https://github.com/angular/angular-cli/releases#release-v22.1.0
angular/angular-cli@0c18dc0
This helps to properly work with Angular's built-in subresource integrity hash generation.
Before Sentry would have changed the files after they have been generated by Angular, breaking the integrity hashes of the files.
Solution Brainstorm
Does this need an update of those two Angular documentation pages?
https://github.com/getsentry/sentry-docs/blob/master/docs/platforms/javascript/common/sourcemaps/uploading/angular-nx.mdx
https://github.com/getsentry/sentry-docs/blob/master/docs/platforms/javascript/common/sourcemaps/uploading/angular-webpack.mdx
We've been using nx with the Sentry CLI, so we simply stopped using the CLI, however, is there any option to disable the debug ID generation for Angular?