ref(nextjs): Don't use Sentry Webpack Plugin in dev mode#7901
Merged
ref(nextjs): Don't use Sentry Webpack Plugin in dev mode#7901
Conversation
Contributor
size-limit report 📦
|
Lms24
approved these changes
Apr 19, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Because we're now using Next.js source map resolving server for dev mode we don't need to run the webpack plugin at all in dev mode to get resolved stack traces.
If the plugin isn't silenced in the options it is extremely noisy in dev mode without doing anything. This PR fixes that.