Source Maps

@sentry/nuxt uses the Sentry Vite Plugin and the Sentry Rollup Plugin to generate and upload source maps automatically. This means that when you run a production build (nuxt build), source maps will be generated and uploaded to Sentry, so that errors in Sentry will contain readable stack traces.

Configure Source Maps Upload

To automatically upload source maps, you need to provide your Sentry auth token, your organization, and project slugs to the sentry.sourceMapsUploadOptions in your Nuxt config:

export default defineNuxtConfig({
  modules: ["@sentry/nuxt/module"],
  sentry: {
    sourceMapsUploadOptions: {
      org: "example-org",
      project: "example-project",
      authToken: "sntrys_YOUR_TOKEN_HERE",
    },
  },
});

Enabling Client-side Source Map Generation

To enable client-side source maps, you need to do so explicitly. Nuxt applies default source map settings, and the Sentry Nuxt Module respects these when they are defined.

To enable client-side source map generation, add the following to your Nuxt configuration:

export default defineNuxtConfig({
  sourcemap: { client: "hidden" },
});

The hidden option functions the same as true, by enabling source map generation. However, it also suppresses the source map reference comments that normally appear at the end of each generated file in the build output. This option keeps the source maps available without exposing their references in the files.

When you open your browser's developer tools, the browser tries to fetch source maps using the reference comments found in bundled files. If the source maps are uploaded to Sentry and removed from the client side, these references cause 404 errors in the developer tools. The hidden option stops these comments from being generated, preventing browsers from trying to fetch missing files and avoiding unnecessary errors.

Additional Resources

• Using sentry-cli to Upload Source Maps
• 4 Reasons Why Your Source Maps Are Broken
• Debug Your Node.js Projects with Source Maps