[@sentry/nextjs] Rely on recent nextjs / webpack 5 sourcemaps

[belgattitude]

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• Provide a link to the affected event from your Sentry account

Package + Version

• @sentry/nextjs

Version:

6.10.0

Description

It seems (and sorry I'm not totally sure of it), that sentry/nextjs relies on webpack4 (through @sentry/webpack-plugin)... Reference getsentry/sentry-webpack-plugin#296.

Recent version of nextjs 10.2+ /webpack 5 are already able to generate source-maps... would it make sense to re-use them ?

[lobsterkatie]

Hi, @belgattitude. I'm not quite sure what you mean by

Recent version of nextjs 10.2+ /webpack 5 are already able to generate source-maps... would it make sense to re-use them ?

What do sourcemaps have to do with whether the sentry plugin relies on types from webpack 4.x or 5.x (which is what the issue you mentioned is about)?

[kamilogorek]

The types should be compatible with v4 and v5 of webpack. Please see getsentry/sentry-webpack-plugin#296 (comment) and it's referenced issues. Cheers!