Sentry doesn't respect next.js `basePath` config when resolving stack frames

[simon-abbott]

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.69.0

Framework Version

13.4.4

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

1. In next.config.js set basePath: '/some/path', and use withSentryConfig as normal
2. Trigger some client-side error in dev mode

Expected Result

The error metadata should be fetched correctly.

Actual Result

Sentry tries to fetch /__nextjs_original-stack-frame instead of /some/path/__nextjs_original-stack-frame, causing a 404 error.

[simon-abbott]

I've traced the issue to this fetch:

sentry-javascript/packages/nextjs/src/common/devErrorSymbolicationEventProcessor.ts

Lines 31 to 35 in cd0bc3b

	const res = await fetch(
	`${
	// eslint-disable-next-line no-restricted-globals
	typeof window === 'undefined' ? 'http://localhost:3000' : '' // TODO: handle the case where users define a different port
	}/__nextjs_original-stack-frame?${params.toString()}`,

[AbhiPrasad]

Does this error happen when you build the app for production?

[simon-abbott]

No, it does not. In fact, no call to __nextjs_original-stack-frame is made at all. But that doesn't surprise me seeing as the relevant code I found is in a file called devErrorSymbolicationEventProcessor.ts

[Lms24]

Thanks for investigating! Would you be interested in opening a PR, given that you already took the time to debug where this happens? If not, no worries. We'll backlog it and fix it (can't give you an ETA, though).