Fix Sentry sourcemaps (#11051)
The method used for uploading release artifacts to Sentry has been updated to allow `sentry-cli` to associate our minified bundles with the corresponding source map file. This should help Sentry display rich stack traces. Previously Sentry had used the `sourceMappingURL` to associate source maps with bundles, but we recently removed this in #10695. The hope is that this change to the upload process will ensure the mapping works correctly without the `sourceMappingURL` comment. The `upload_bundles` function was removed because the later `upload_sourcemaps` function actually uploaded both the bundles and source maps. The `--rewrite` flag was added to enable a newer "rewrite" feature of the Sentry CLI that they recommend using [1]. This rewrite is where they associate source maps with bundles. The `url-prefix` has been updated to be `metamask` rather than `sourcemaps`. I don't think `sourcemaps` was ever the correct prefix. We normalize our errors to have the path `metamask/` before sending any reports to Sentry. [1]: https://docs.sentry.io/product/cli/releases/#sentry-cli-sourcemapsfeature/default_network_editable
parent
dfe5df765e
commit
1675c047c7
Loading…
Reference in new issue