docs(nextjs): Move webpack build config under webpack namespace
#15691
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
|
Bundle ReportChanges will decrease total bundle size by 396.13kB (-1.12%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
view changes for bundle: sentry-docs-edge-server-array-pushAssets Changed:
|
inventarSarah
approved these changes
Dec 4, 2025
Collaborator
inventarSarah
left a comment
inventarSarah
left a comment
There was a problem hiding this comment.
👍looks good to me
docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx
Outdated
Show resolved
Hide resolved
| have no effect. The Sentry SDK will no longer apply build-time instrumentation | ||
| and will rely purely on Next.js telemetry features. | ||
| </Alert> | ||
|
|
Collaborator
There was a problem hiding this comment.
I think we can remove the alert about Turbopack in the lines above. wdyt?
This one:
<Alert level="info">
If you're building your Next.js application with Turbopack, this option will
have no effect. The Sentry SDK will no longer apply build-time instrumentation
and will rely purely on Next.js telemetry features.
</Alert>
Collaborator
Author
There was a problem hiding this comment.
Yep, absolutely 💯
…dex.mdx Co-authored-by: Sarah Mischinger <[email protected]>
logaretm
force-pushed
the
awad/deprecate-webpack-toplevel-options-docs
branch
from
f94a4f6 to
9074117
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
This PR reorganizes the Next.js SDK build configuration documentation by moving webpack-specific options under a webpack namespace. This improves clarity about which options are relevant for Turbopack builds versus Webpack builds.
- Moves webpack-specific configuration options (
autoInstrumentServerFunctions,autoInstrumentMiddleware,autoInstrumentAppDirectory,excludeServerRoutes,automaticVercelMonitors,unstable_sentryWebpackPluginOptions, andreactComponentAnnotation) under a new "Next.js Webpack Options" section - Adds a clear alert indicating these options only take effect when using Webpack
- Reorganizes the documentation structure to distinguish between general options and webpack-specific options
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx
Outdated
Show resolved
Hide resolved
![sentry[bot]](https://avatars.githubusercontent.com/u/1396951?s=60&v=4){kind=small}
docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx
Outdated
Show resolved
Hide resolved
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.
We are moving the only-webpack related configurations under
webpacknamespace to better fit our goal of communicating the SDK readiness for Turbopack by default.This involved moving several options to be nested under a
webpackpath in the build configuration.This is meant to be released once this getsentry/sentry-javascript#18343 goes live, so I will keep this open until then. Will keep it in draft as well.
The SDK PR adds warnings for those deprecated options and warns users about using them if detected so I don't think we need to do that here once it goes live.