Runtime errors after upgrading to `@sentry/vite-plugin@4.0.1`

[alSergey]

Environment

• @sentry/vite-plugin@4.0.1
• @sentry/vue@9.44.2
• nuxt@3.17.5
• vite@6.3.5

Steps to Reproduce

It's quite difficult to describe the steps to reproduce because the issue doesn't occur across all projects. I'll try to explain what I discovered.

I'm using Nuxt with the Vite bundler. After upgrading from @sentry/vite-plugin@4.0.0 to @sentry/vite-plugin@4.0.1, I started encountering a runtime error when launching the service:

ReferenceError: Cannot access 'k' before initialization

When I checked the line where the code fails, I saw the following:

(function() {
    var e = typeof k < "u" ? k : typeof global < "u" ? global : typeof globalThis < "u" ? globalThis : typeof self < "u" ? self : {}; // The error occurs on this line
    e.SENTRY_RELEASE = {
        id: "first-project"
    }
}
)();

For unclear reasons, the variable k appears in the code, even though when checking your source code, it's explicitly written as window, and there's no mention of k. As far as I understand, this code is further processed by Vite, and for some reason, window is being replaced with k.

Interestingly, in another Nuxt project where I'm also using @sentry/vite-plugin@4.0.1, everything works correctly. There are no significant differences between the two projects. Here's an example of the working code:

(function() {
    var e = typeof window < "u" ? window : typeof global < "u" ? global : typeof globalThis < "u" ? globalThis : typeof self < "u" ? self : {};
    e.SENTRY_RELEASE = {
        id: "second-project"
    }
}
)();

Additional information

1. Here’s an example from the first project using @sentry/vite-plugin@4.0.0:

{
    let e = typeof window < "u" ? window : typeof global < "u" ? global : typeof globalThis < "u" ? globalThis : typeof self < "u" ? self : {};
    e.SENTRY_RELEASE = {
        id: "first-project"
    }
}

2. I also tried upgrading to @sentry/vite-plugin@4.0.2, and the issue persists.

3. If you run the erroneous code in the console, there is no error and everything works correctly:

Expected Result

No runtime errors

Actual Result

Runtime errors occur

[linear]

BUNDLER-77 Runtime errors after upgrading to `@sentry/vite-plugin@4.0.1`

[s1gr1d]

Hello,
you wrote

in another Nuxt project where I'm also using @sentry/vite-plugin@4.0.1, everything works correctly
Do you maybe have a different Vite/Rollup version installed in those projects? Specifically, the version that is present in the lock file.

And in general, we have an SDK specifically for Nuxt. By installing this SDK, you don't need to set up the bundlers yourself as the SDK includes this all under the hood. Or is there a specific reason why you are using @sentry/vue with the bundler plugin?

[alSergey]

Do you maybe have a different Vite/Rollup version installed in those projects? Specifically, the version that is present in the lock file.

In the project where everything works correctly, the dependencies are almost identical:

• @sentry/vite-plugin@4.0.2
• @sentry/vue@9.44.0
• nuxt@3.17.5
• vite@6.3.5

Or is there a specific reason why you are using @sentry/vue with the bundler plugin?

There are two reasons why I continue using @sentry/vue along with @sentry/vite-plugin:

• The @sentry/nuxt package is still in beta status
• The project is old and was created before the @sentry/nuxt package even existed

[s1gr1d]

Are those the dependencies in your package.json or in the lock file?
You can easily grep the deps from the lock file with grep -i 'vite' pnpm-lock.yaml (or yarn.lock or whatever lock file you have).

But the Vite dependency is a different one. Does it work when you downgrade Vite?

---

And about the Sentry Nuxt SDK:

• it's still shown as beta, but it's basically done already and will be officially released soon. So it's safe to use :)
• using it on an old project is no problem either. The only important thing is, that you are using ideally Nuxt 3.14.0+ (which you are)