[Nuxt] Inject debug IDs and release only at build-end

Description

Problem

Nuxt runs through the build twice (client and server).

Nuxt builds client-side
Nuxt builds server-side
Now all client and server files in .nuxt/dist contain one debug ID
Nitro builds server-side
The whole build output is moved to .output and the server-side files which were already included in .nuxt/dist/server (the Nuxt build) are touched by the rollup plugin a second time.

This setup causes the Nuxt SDK to include the Vite and the Rollup plugin, so all source map files are uploaded. However, this has some drawbacks:

build-times are longer (as there are more uploads during the build)
Source-mapping might cause problems because some files are touched twice (by Nuxt and Nitro) (related issue - however, this was fixed with a workaround that checks if a file already contains a debug ID)
release injection happens twice in some files

Solution

By using the Bundler Plugin Manager, we can do everything (debug
ID and release injection) at the end of the build.

JS-1551

Is this still planned? The check from getsentry/sentry-javascript-bundler-plugins#827 doesn't fully fix #18519. It reproduces on a fresh Nuxt 4.5.2 app (4 pages) with @sentry/nuxt 10.71.0 and 11.1.0:

13 of 23 files in .output/server keep only the Vite chunk's debug ID. The snippet is within the first 6000 chars, so Nitro skips its own, and two different files with different source maps get uploaded under one ID.
chunks/virtual/entry.mjs ends up with 5 IDs: Nitro's own plus 4 Vite ones further down. The last registered Vite ID wins.

Either way, server frames resolve with another file's source map. In our app the wrong location shifts with every build, so the same server error opens a new issue on every release.

Registering the Vite plugin for the client only (server: false in the addVitePlugin call in setupSourceMaps) fixes it on both versions: each server file gets exactly one debug ID of its own.

Hi,
Thanks for sharing the problem you're facing. I'm gonna take another look at this!

fix(nuxt): Do not inject debug IDs into the SSR build (#25080)

Fix will be released in 11.5.0 and 10.76.1

fix(v10/nuxt): Do not inject debug IDs into the SSR build (#25094)

A PR closing this issue has just been released 🚀

This issue was referenced by PR #25080, which was included in the 11.5.0 release.

Navigation Menu

Repository navigation

[Nuxt] Inject debug IDs and release only at build-end #18974

Description

Problem

Solution

A PR closing this issue has just been released 🚀

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

[Nuxt] Inject debug IDs and release only at build-end #18974

Description

Description

Problem

Solution

Activity

linear commented on Jan 26, 2026

andreyshivas commented on Sep 30, 2026

s1gr1d commented on Oct 2, 2026

s1gr1d commented on Oct 6, 2026

github-actions commented on Oct 7, 2026

A PR closing this issue has just been released 🚀

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions