[@sentry/nextjs] Sentry CLI panics during source map upload after production build

[devalentineomonya]

During production build of our Next.js project, the Sentry CLI panics while uploading source maps. This prevents the upload process from completing, resulting in incomplete source maps in Sentry.

Steps to Reproduce:

1. Install the following Sentry packages:

   • @sentry/nextjs ^10.30.0
   • @sentry/profiling-node ^9.47.1
   • @sentry/wizard ^5.4.0

2. Configure Sentry in a Next.js project with a valid DSN and release.

3. Build the project for production using:

   bun run --bun next build

4. Observe the Sentry CLI panic during source map upload, with output similar to:

   2: std::panicking::panic_handler::{{closure}}
   3: std::sys::backtrace::__rust_end_short_backtrace
   4: __rustc::rust_begin_unwind
   ...
   Error: Command --header sentry-trace:... --header baggage:...
   

Expected Behavior:
Source maps upload successfully without any CLI panic.

Actual Behavior:
The Sentry CLI panics with a Rust backtrace, preventing the upload of source maps.

Project Environment:

• Next.js: 16.0.10
• React: 19.2.3
• Node.js runtime: Bun
• Turbopack: true
• @sentry/nextjs: 10.30.0
• @sentry/profiling-node: 9.47.1
• @sentry/wizard: 5.4.0
• Platform: Vercel

Build & Deployment Scripts:

"scripts": {
  "dev": "bun run --bun next dev",
  "build": "bun run --bun next build",
  "start": "bun run --bun next start",
  "postbuild": "next-sitemap"
}

[linear]

CLI-255

[szokeasaurusrex]

Hi @devalentineomonya, thank you for reporting this problem, and thanks for your patience with slower response times over the holidays.

From the backtrace, it looks like there is some OS error when printing to stdout which is causing the panic.

Is this error persistent, or did it only happen once? If it was a one-off problem, then I think we can probably safely close this issue; I/O errors when printing to stdout should probably be rare enough that handling them is not worth it.

If the issue was persistent, can you please elaborate on any specific configurations which might help me to reproduce this error? Also, please provide the full logs from your build, or at least, the full logs from the Sentry CLI step, in a plaintext (not screenshot) format, if you need further assistance.

[devalentineomonya]

This happened while doing a build on vercel,, it happened for 3 builds on the same day, I've not deployed since then, might have been a problem on their end I can't verify though

[devalentineomonya]

Hi @szokeasaurusrex it happened again today as I was deploying the same project on vercel,, seem it's not just something with them there might be a real issue

[szokeasaurusrex]

@devalentineomonya thank you for letting me know. Does the failure consistently fail in the same part of the run, or is it random where exactly it occurs?

Also, could you please provide the full logs from one of the runs where you observed this failure, in plaintext (not a screenshot)? 🙏

[szokeasaurusrex]

Also, what version of Bun are you using?