@sentry/nextjs: `hideSourceMaps: false` doesn't work for vercel previews

[11bit]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/nextjs

SDK Version

7.16.0

Framework Version

12.3.1

Link to Sentry event

No response

Steps to Reproduce

1. Add an option to not hide source-maps

 sentry: {
 hideSourceMaps: false,
 }

2. Deploy to vercel preview and capture any exception

Expected Result

Source-maps visible

Actual Result

Source-maps invisible

Note: I can make it work by adding disableClientWebpackPlugin: false. But is not documented anywhere

Thanks!

[lobsterkatie]

Hi, @11bit.

When you say the sourcemaps are invisible, do you mean that when you visit your deployed site in the browser, Chrome isn't picking up the sourcemaps in dev tools? Or do you mean sourcemaps aren't working in Sentry to demangle your errors?

Also, when you're deploying to vercel, is it a production deployment?

[11bit]

When you say the sourcemaps are invisible, do you mean that when you visit your deployed site in the browser, Chrome isn't picking up the sourcemaps in dev tools? Or do you mean sourcemaps aren't working in Sentry to demangle your errors?

Yes, when I visit deployed site in the browser, Chrome isn't picking up the sourcemaps. And there is no sourcemap record at the bottom of minified js files

Also, when you're deploying to vercel, is it a production deployment

It's preview deployment. And the behavior changed after I updated @sentry/next from 6.19.7 to7.16.0

[lobsterkatie]

Also, when you're deploying to vercel, is it a production deployment

It's preview deployment. And the behavior changed after I updated @sentry/next from 6.19.7 to7.16.0

Ah, yes, you did say that originally, sorry! This is expected behavior. In general, sourcemaps shouldn't be uploaded to Sentry for anything but prod deployments, because it creates a record of a release, which is generally not what you want if you're just deploying a preview version. (For example, our docs are hosted on Vercel, and a preview deployment is created every time someone opens a PR or pushes to an existing PR. If a release were created in Sentry each time that happened, the idea of a release would become meaningless.) This is why we turn it off by default. My suggestion would be to set dryRun to true in your sentryWebpackPluginOptions in next.config.js when you're in a preview environment.

That said, you've pointed out an in-between case which we don't currently handle, and probably should. Just because we're not uploading sourcemaps to Sentry doesn't mean we couldn't let you enable them in Chrome. I've added this to our backlog to fix.

I've added an issue to improve the documentation here: getsentry/sentry-docs#5690.

[11bit]

Thank you for the great explanation!

[lforst]

Am I correct in the assumption that this issue/question is resolved?

[11bit]

@lforst yes, as I understand this is expected behavior