neat (nextjs) troubleshoot docs update

[sergical]

DESCRIBE YOUR PR

Closes https://linear.app/getsentry/issue/FE-640/update-troubleshooting-docs-to-include-version-pinning-for-20

Before

 ⚠ ./node_modules/.pnpm/@[email protected]_@[email protected]_@opentelemetry+context-async-hooks@2_8844bd1bb4ea0490b75ddbff1cecdd6d/node_modules/@sentry/node-core/build/cjs/sdk
Package import-in-the-middle can't be external
The request import-in-the-middle matches serverExternalPackages (or the default list).
The package resolves to a different version when requested from the project directory (2.0.0) compared to the package requested from the importing module (1.14.4).
Make sure to install the same version of the package in both locations.


 ⚠ ./node_modules/.pnpm/@[email protected]_@[email protected]/node_modules/@opentelemetry/instrumentation/build/esm/platform/node
Package require-in-the-middle can't be external
The request require-in-the-middle matches serverExternalPackages (or the default list).
The package resolves to a different version when requested from the project directory (8.0.1) compared to the package requested from the importing module (7.5.2).
Make sure to install the same version of the package in both locations.

After

Nada

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

• Urgent deadline (GA date, etc.):
• Other deadline:
• None: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
  Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
sentry-docs	Ready	Preview	Comment	Nov 7, 2025 9:48pm

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
develop-docs	Ignored			Nov 7, 2025 9:48pm

[sergical]

Closes FE-640

[codecov]

Bundle Report

Changes will increase total bundle size by 723 bytes (0.0%) ⬆️. This is within the configured threshold ✅

Detailed changes

Bundle name	Size	Change
sentry-docs-client-array-push	10.16MB	-6 bytes (-0.0%) ⬇️
sentry-docs-server-cjs	12.58MB	729 bytes (0.01%) ⬆️

Affected Assets, Files, and Routes:

view changes for bundle: sentry-docs-server-cjs

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
1729.js	-3 bytes	1.74MB	-0.0%
../instrumentation.js	-3 bytes	1.07MB	-0.0%
9523.js	-3 bytes	1.04MB	-0.0%
../app/[[...path]]/page.js.nft.json	246 bytes	760.88kB	0.03%
../app/platform-redirect/page.js.nft.json	246 bytes	760.79kB	0.03%
../app/sitemap.xml/route.js.nft.json	246 bytes	758.02kB	0.03%

view changes for bundle: sentry-docs-client-array-push

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
static/chunks/pages/_app-*.js	-3 bytes	882.71kB	-0.0%
static/chunks/8321-*.js	-3 bytes	425.87kB	-0.0%
static/Qg94UfATmXqYvjYhbMvwn/_buildManifest.js (New)	684 bytes	684 bytes	100.0% 🚀
static/Qg94UfATmXqYvjYhbMvwn/_ssgManifest.js (New)	77 bytes	77 bytes	100.0% 🚀
static/lmzVl-*.js (Deleted)	-77 bytes	0 bytes	-100.0% 🗑️
static/lmzVl-*.js (Deleted)	-684 bytes	0 bytes	-100.0% 🗑️

[linear]

FE-640 Update troubleshooting docs to include version pinning for 2.0

[BYK]

I think mentioning the version pinning with some rationale or future plans would provide good context

[timfish]

Next time we bump out otel deps this will become v2 and v8