This repository has been archived by the owner on May 14, 2024. It is now read-only.
Fix sourcemaps association #1630
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We don't need to set `productionBrowserSourceMaps` because the Sentry Webpack plugin always assumes that to be true. - @sentry/nextjs withSentryConfig enables productionBrowserSourceMaps, in the end, assets sourcemap is open to the public vercel/next.js#32920 - @sentry/nextjs will generate and upload source maps automatically https://docs.sentry.io/platforms/javascript/guides/nextjs/sourcemaps/
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The reason why Sentry was not showing sourcemaps was because the release value used by the Sentry Webpack plugin at buildtime (autogenerated) was different from the release value that Sentry.init at runtime (git SHA).