Skip to content

docs(js): Update nextjs docs on tunnelRoute option #14066

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 8, 2025
Merged

docs(js): Update nextjs docs on tunnelRoute option #14066

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a065eb0
update next docs on tunneling option
chargome Jun 18, 2025
eeefe88
update middleware note
chargome Jul 8, 2025
658364c
beepboop
chargome Jul 8, 2025
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
8 changes: 3 additions & 5 deletions docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -222,12 +222,10 @@ 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="Complications with Next.js middleware">
Client-side event recording will fail if your Next.js middleware intercepts
the configured route. To prevent this, exclude the tunnel route by adding a
negative matcher to your middleware like `(?!monitoring-tunnel)`.
<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.

In the case of auto-generated routes, the route is unpredictable and changes with each deployment. Instead of using a negative matcher, you can add an allowlist of matchers for the routes you want your middleware to handle or fallback to a custom static path.
If you're not using Turbopack, Sentry will automatically skip the tunnel route in your middleware.
</Expandable>

</SdkOption>
Expand Down