Sentry causes Next.js standalone to copy entire repo into build output

[BTOdell]

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

10.21.0

Framework Version

Next 16.0.0

Link to Sentry event

No response

Reproduction Example/SDK Setup

https://github.com/BTOdell/sentry-nextjs-standalone-bug

Steps to Reproduce

1. Set Next.js build output to 'standalone'
2. Import Sentry SDK from instrumentation.ts (don't even need to configure Sentry in next.config.ts)

Expected Result

Next.js standalone build output should only contain the minimal files needed to run the app

Actual Result

Standalone output directory contains copy of the entire repository / project

Additional Context

Confirmed that this bug does not happen with Next 15.4.4 with @sentry/nextjs v9 nor v10.
Likely a compatibility issue with Next 16?

May be related to #18001, but I'm not getting a build error - just incorrect build output.

_{Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1080

[chargome]

Hey @BTOdell thanks for filing this. We'll likely need to take this to the Next.js team as we do not control the build ouput. I assume you're building the app with Turbopack atm?

[BTOdell]

@chargome Yeah, I understand you'll probably need to work with the Next.js team to figure out why this is happening. The minimal repo that I included was stripped down from an app in production and Sentry was the only dependency that was causing this bug to happen.

[chargome]

Thanks for investigating! We have some other bundling related issues with turbopack atm, maybe they're related. Will post any updates here