@sentry/nextjs: is the webpack plugin/configuration necessary?

[soulprovidr]

Hi all,

First of all, thank you for your work on Sentry – it's a great service.

I'm trying to set up Sentry with an existing Next.js application, but I am finding that the 'architecture' or functionality of @sentry/nextjs is not totally clear to me.

I am aiming for a super minimal setup where uncaught errors on the client and on the server are sent to Sentry and stored for further triage by the team. Is it necessary to use and configure sentry-webpack-plugin for this purpose?

From looking at the source code, it seems like the Webpack plugin is mostly (only?) concerned with Sentry's "Releases" feature, and ideally I would like to avoid adding 5-6 environment variables (or managing sentry.properties) just to log errors when we are currently not interested in using this feature.

Thanks!

[HazAT]

If you want to use it together with source maps;
The Webpack plugin ensures you upload your source maps to Sentry so we can present you with a stack trace and readable code vs. minified Javascript.

If it's enough for you to see minified code you could get rid of a few parts but it's not a good experience debugging your errors.

Hope this helps, cheers.

[lobsterkatie]

Hi, @soulprovidr.

I'll second what Daniel said - using sentry is 100x better with sourcemaps, and so I'd encourage you to keep the webpack plugin turned on. That said, there's now an option to turn it off. Docs are here.

[soulprovidr]

Hi, @soulprovidr.

I'll second what Daniel said - using sentry is 100x better with sourcemaps, and so I'd encourage you to keep the webpack plugin turned on. That said, there's now an option to turn it off. Docs are here.

Thanks @lobsterkatie – the new documentation and configuration options are very helpful!