Nuxt: Compatibility with different Deployment Platforms

[s1gr1d]

Description

The Sentry Nuxt SDK should work on different deployment platforms. This issue tracks the progress of what we already tested and implemented.

The state shows what is supported from v8.35.0 (beta) onwards.

If you experience issues or a specific deployment platform is not listed, feel free to comment here or file a new GitHub issue.

Local Production Build (nuxi build -> node .output/server/index.mjs)

Preview Give feedback

1. Client-side error monitoring works
2. Client-side tracing works
3. Server-side error monitoring works
4. Server-side tracing works

Netlify

Preview Give feedback

1. Client-side error monitoring works
2. Client-side tracing works
3. Server-side error monitoring works
4. Server-side tracing works
5. Server-side logs work

Vercel

Preview Give feedback

1. Client-side error monitoring works
2. Client-side tracing works
3. Server-side error monitoring works
4. Server-side tracing works

Cloudflare (not tested yet)

Preview Give feedback

1. Client-side error monitoring works
2. Client-side tracing works
3. Server-side error monitoring works
4. Server-side tracing works
5. Nuxt vs Cloudflare interop #13949
   Package: cloudflare Package: nuxt +2

[rocketiscool]

Any idea why I get

[nuxt] [request error] [unhandled] [500] ENOENT: no such file or directory, open 'path/web/apps/web/.output/public/_nuxt/yrDNp5yz.js.map'

on original page load with local production build

Edit:

Seems that unless

    sourcemap: {
        server: true,
        client: true
    },

both server and client are explicitly enabled, it will cause that error if its just client: true alone.

[s1gr1d]

Are you using version 8.35.0? Nuxt automatically sets sourcemap.server: true, so this shouldn't make a difference 🤔 Do you have a small reproduction example?