Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -83,10 +83,10 @@ You can optionally re-throw the error to fail the build process.
withSentryConfig(nextConfig, {
// ... other options
errorHandler: (error) => {
console.warn('Sentry build error occurred:', error);
console.warn("Sentry build error occurred:", error);
// Optionally, you can still fail the build by re-throwing the error
// throw error;
}
},
});
```

Expand Down Expand Up @@ -241,9 +241,12 @@ This option can be set to:
Learn more about tunneling in the <PlatformLink to="/troubleshooting/#dealing-with-ad-blockers">troubleshooting section</PlatformLink>.

<Expandable level="warning" title="Using Next.js middleware on Turbopack">
If you're using Turbopack, client-side event recording will fail if your Next.js middleware intercepts the configured tunnel route. To fix this, set the route to a fixed string (like `/error-monitoring`) and add a negative matcher like `(?!error-monitoring)` in your middleware to exclude the tunnel route.

If you're not using Turbopack, Sentry will automatically skip the tunnel route in your middleware.
If you're using Turbopack, client-side event recording will fail if your
Next.js middleware intercepts the configured tunnel route. To fix this, set
the route to a fixed string (like `/error-monitoring`) and add a negative
matcher like `(?!error-monitoring)` in your middleware to exclude the tunnel
route. If you're not using Turbopack, Sentry will automatically skip the
tunnel route in your middleware.
</Expandable>

</SdkOption>
Expand All @@ -261,13 +264,26 @@ Disables automatic injection of the route manifest into the client bundle.
The route manifest is a build-time generated mapping of your Next.js App Router routes that enables Sentry to group transactions by parameterized route names (e.g., `/users/:id` instead of `/users/123`, `/users/456`, etc.).

**Disable this option if:**

- You want to minimize client bundle size
- You're experiencing build issues related to route scanning
- You prefer raw URLs in transaction names
- You're only using the Pages Router (this feature is only supported in the App Router)

</SdkOption>

<SdkOption name="reactComponentAnnotation.enabled" type="boolean" defaultValue="false">

Enables React component name tracking. When enabled, it annotates React components with data attributes that allow Sentry to track which components users interacted with in features like Session Replay and breadcrumbs.

</SdkOption>

<SdkOption name="reactComponentAnnotation.ignoredComponents" type="string[] | undefined">

A list of React component names to exclude from component annotation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth giving an example of how this list string is formatted? Are the component names comma separated? Separated by spaces?


</SdkOption>

<SdkOption
name="unstable_sentryWebpackPluginOptions"
type="SentryWebpackPluginOptions"
Expand Down