SourceMap header or sourceMappingUrl comment for static sites?

[bmulholland]

I have configured publishRelease, and that is working: the release is pushed to Sentry, and source code (and maps) are uploaded to the project. Nevertheless, the mapping isn't working: Sentry tells me "Source code was not found"

Now, looking at their troubleshooting tips, they suggest checking for sourceMappingUrl - and that isn't set. Looking at the sentry-webpack-plugin docs, the default is to use a SourceMap header - and that header is not set on my production server. Likewise, sourceMappingUrl comments are not added. sentry-webpack-plugin includes notes on how to disable the SourceMap header -- assuming sourceMappingUrl is set in all the files -- but there's no mention of how to do that anywhere in this plugin, in sentry-webpack-plugin, or in sentry-cli.

Questions:

• I feel like I must be missing something? How am I the first person to run into this?
• Is the expectation of this plugin that nuxt is serving the files, and thus setting the SourceMap header?
• If I'm hosting my site statically, do I need to set the sourceMappingUrl somehow? Or is there some clever way to server the SourceMap header?
• How do I get the sourceMappingUrl added to the generated assets?

Configuration (yes, all env vars are properly set, as confirmed by the source files making it to Sentry fine):

    sentry: {
      dsn: process.env.SENTRY_DSN,
      // Enable performance tracing
      tracing: {
        // 1.0 = 100% of requests will be sampled, so 0.2 = 20%
        tracesSampleRate: 0.2,
      },
      // Send source maps to Sentry for better error messages
      publishRelease: {
        authToken: process.env.SENTRY_AUTH_TOKEN,
        org: process.env.SENTRY_ORG,
        project: process.env.SENTRY_PROJECT,
      },
      // https://sentry.nuxtjs.org/sentry/options/#sourcemapstyle
      // most people, that should be a better option but due to it being a
      // breaking change, it won't be set as the default until next major
      // release
      sourceMapStyle: "hidden-source-map",
    },

[rchl]

Documentation suggests setting sourceMapStyle to hidden-source-map but I'm not actually sure if that works correctly with sentry.

Can you try removing the sourceMapStyle option so that it uses source-map instead. Then the source files should include //# sourceMappingURL comment at the end.

[rchl]

The browser generates the stack trace initially and then it's captured by Sentry.

Nuxt doesn't do any post-processing for client-side error I believe.

Sentry might be doing post-processing but I'm not sure if on the client, before sending or after the crash is sent to Sentry.

Though it appears to me now that the stack you've posted in #369 (reply in thread) is already processed since it contains node_modules paths rather just the paths to the bundle.

Can you post the stack trace from the issue with those buttons selected?

The minified view is the original stack trace as reported by the browser, I believe. The original is already processed by Sentry (or source mapped).

[bmulholland]

Minified looks similar:

TypeError: this.comparison is null
  at revised(File@https://example.com/_nuxt/2969e7f.js:1:9933)
  at kn.prototype.get(/_nuxt/e252db4.js:2:27382)
  at kn.prototype.evaluate(/_nuxt/e252db4.js:2:28522)
  at Pn/<(/_nuxt/e252db4.js:2:30411)
  at fn(/_nuxt/2969e7f.js:1:11146)
  at r(/_nuxt/e252db4.js:2:15927)
  at Ie(/_nuxt/e252db4.js:2:16765)

I'm going to try again without the URL prefix set and see what values I get on both sides.

[bmulholland]

After a lot of trial and error, all appears working -- with the default config, no less -- now.

I'm pretty sure the only real diff since I started working on it is removing nuxt/emotion - which we weren't even using. I removed it as suspect because it claims source maps as one of its features, and that seems to have been the case...

[bmulholland]

Okay, I tried re-adding emotion and still everything is working. So at the end, I've changed literally nothing and it's now working where it wasn't before?

I'm out of ideas for what the issue could have been, or where those File@'s were coming from, so I guess we'll never know...

Thanks again for all your help, that was a weird one and I couldn't have done it without you.

[bmulholland]

Oh, to try to give some value back: I am using hidden-source-maps and that seems to be working well.