NextJS Webpack Plugin not including all relevant sourcemaps

[FabianKoder]

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

9.22.0

Framework Version

Next 15.3.0

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

We recently migrated to the Webpack plugin and used to upload the sourcemaps using a GitHub Action - since the migration, we have many issues that throw "In App" but sourcemaps are only available up to a certain point. Previously, the same issues had 100% sourcemap coverage.

As seen here, main-*.js gets explicitly excluded from the sourcemap upload, even with widenClientFileUpload enabled:

sentry-javascript/packages/nextjs/src/config/webpackPluginOptions.ts

Lines 44 to 52 in 48f1a4f

	// TODO: We should think about uploading these when `widenClientFileUpload` is `true`. They may be useful in some situations.
	sourcemapUploadIgnore.push(
	path.posix.join(distDirAbsPath, 'static', 'chunks', 'framework-*'),
	path.posix.join(distDirAbsPath, 'static', 'chunks', 'framework.*'),
	path.posix.join(distDirAbsPath, 'static', 'chunks', 'main-*'),
	path.posix.join(distDirAbsPath, 'static', 'chunks', 'polyfills-*'),
	path.posix.join(distDirAbsPath, 'static', 'chunks', 'webpack-*'),
	);
	}

It seems some of our code is being bundled in the main bundle (my suspicion is that in this specific case it happens because the safeParse function is also used in instrumentation-client), which is now not available anymore to view.

Expected Result

Being able to see sourcemaps for the main bundle as well

Actual Result

See reproduction steps

[chargome]

Hey @FabianKoder thanks for reaching out!

Assuming you already have set widenClientFileUpload: true in your withSentry config, we can try to widen the scope of this flag. We'll look into it!

[kylemh]

Let me know if there's anything I can provide? I've just setup Sentry with the CLI on a relatively new Next.js App-dir app and had the same results as OP. I had widenClientFileUpload: true (along w/ all the other defaults from the CLI)

If it helps, this is the feedback I'm seeing Sentry Dashboard

[andreiborza]

Hi @kylemh, thanks for writing in.

Just to make sure: Are you deploying the files that have been injected with debug ids, i.e. the files you built are also the files you deployed?

[kylemh]

I follow the Docker template for self-hosting and run the next.js build command. I don't feel like I'm doing anything unique in regards to deploying files. Is that a good answer?