Incorrect `NEXTJS_REQUEST_ASYNC_STORAGE_MODULE_PATH` in Next.js 13.4.20

[Burry]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

7.68.0

Framework Version

13.4.20

Link to Sentry event

No response

SDK Setup

npx @sentry/wizard@latest -i nextjs

Steps to Reproduce

1. Install the Next.js canary release (yarn add next@13.4.20-canary.20) in a project using the Next.js 13 App Directory and Route Handlers.
2. Implement the Sentry plugin in next.config.js.
3. Run next build.
4. Observe a console warning: The Sentry SDK could not access the RequestAsyncStorage module. Certain features may not work. There is nothing you can do to fix this yourself, but future SDK updates may resolve this.
5. Observe an error when building each route handler wrapped by Sentry: Module not found: Can't resolve '@sentry/nextjs/build/esm/config/templates/requestAsyncStorageShim.js'

Expected Result

Next.js should successfully build all Route Handlers wrapped by Sentry

Actual Result

Identified the offending line in packages/nextjs/src/config/loaders/wrappingLoader.ts#L19, which should use next/dist/client/components/request-async-storage.external

[lforst]

@Burry Hey, thanks for reporting this. Can I ask what made you resolve this issue? Were there any learnings?

[joacub]

the error is in the nextjs side aparently, they fixed at canary 13.4.20-canary.21 and broke again in 13.4.20-canary.22

[feedthejim]

It's not a breakage it's just a refactor of internal apis that Sentry is using. The change will be present from canary 22 most likely, so you should update the path you're requiring from.

[joacub]

@feedthejim when you said you , are you refering to me ? or sentry team ?, cause i am not referencing that library at all in my code.

[Burry]

@Burry Hey, thanks for reporting this. Can I ask what made you resolve this issue? Were there any learnings?

Sure thing, reopening it now lol. Vercel initially reverted the changes that led to this issue so I closed it. I missed they took another shot at it in vercel/next.js#55139

[Burry]

No real learnings though, I got frustrated trying to monkeypatch @sentry/nextjs and just stayed on the Next build that reverted the refactor

[joacub]

any advance on this, we get forced to disabled sentry for now due to this, 👯‍♀️