docs(nextjs): added tree-shaking webpack config guide #15790
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
A PR to go in tandem with getsentry/sentry-javascript#18359 once it gets merged and released.
It documents the new tree-shaking options now abstracted away into
webpack.treeshakenamespace. It has a few differences to the existing tree-shaking flags under the hood:trueto take effect, unlike the flags where some had to be set totrueand some had to be set tofalse.webpack.treeshakebuild options rather than needing the user to be aware of the webpack define plugin API.Marking it as a draft to avoid merging it before the PR goes live.