@sentry/nextjs: option for `hidden-source-map` instead of `source-map`

I created a webpack plugin which remove all sourcemaps after sentry’s upload and implement @hellojser solution to remove the sourcemap references to avoid 404 errors by browser calling the unexisting map files

https://github.com/AlexBeauchemin/webpack-delete-sourcemaps-plugin

withSentryConfig which is used to generate the config is nothing else than a function that processes input config, and outputs updated one. There’s nothing that’d stop you from changing any of the values once it’s processed.

Based on this docs: https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#extend-default-webpack-usage-for-source-maps

Given this config (shortened for readabilty):

const { withSentryConfig } = require("@sentry/nextjs");
// ...
module.exports = withSentryConfig(moduleExports, SentryWebpackPluginOptions);

You can write:

const { withSentryConfig } = require("@sentry/nextjs");
// ...
const sentryConfig = withSentryConfig(moduleExports, SentryWebpackPluginOptions);
const stashedWebpackConfig = sentryConfig.webpack;
sentryConfig.webpack = (config, options) => {
  const updatedConfig = stashedWebpackConfig(config, options);
  // see: https://github.com/vercel/next.js/blob/master/errors/improper-devtool.md
  if (!options.dev) {
    updatedConfig.devtool = 'hidden-source-map';
  }
  return updatedConfig;
}
module.exports = sentryConfig;

While definitely not perfect, it should let you get unblocked.