NextJS: When using static exports (output: 'export'), Sentry unnecessarily uploads node and edge artifact bundles

[metalmarker]

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

8.8.0

Framework Version

Next 14.2.3, React 18.3.1

Link to Sentry event

No response

SDK Setup

N/A

Steps to Reproduce

I'm using NextJS static exports (output: 'export' in next.config.js) to build my application. Everything works as expected, however, during the build process, Sentry unnecessarily uploads the Node and Edge artifact bundles to Sentry.

As per the Opt Out of Sentry SDK bundling in Client- or Server-Side, I do not have sentry.server.config.js and sentry.edge.config.js or an instrumentation.js file.

v7 of the SDK used to have a disableServerWebpackPlugin option, but it has been removed.

In case this is not a bug but a configuration issue, what is the right way to upload only the client artifact bundles when using static exports?

Expected Result

Node and Edge artifact bundles should not be loaded when using static export.

Actual Result

Only client artifact bundles should be loaded when using static export.

[AbhiPrasad]

We have to improve the docs for this page.