From 00da73551e4b8d596ca4aac77d0e0a486dd62dce Mon Sep 17 00:00:00 2001 From: Luke Harries Date: Thu, 31 Dec 2020 12:28:26 +0000 Subject: [PATCH] fix with-sentry by replacing withSourceMaps with productionBrowserSourceMaps removed the `withSourceMaps` package and changed to use `productionBrowserSourceMaps: true` --- examples/with-sentry/next.config.js | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/examples/with-sentry/next.config.js b/examples/with-sentry/next.config.js index 1579ed872c5095..96d8cd909a0a1a 100644 --- a/examples/with-sentry/next.config.js +++ b/examples/with-sentry/next.config.js @@ -1,7 +1,3 @@ -// Use the hidden-source-map option when you don't want the source maps to be -// publicly available on the servers, only to the error reporting -const withSourceMaps = require('@zeit/next-source-maps')() - // Use the SentryWebpack plugin to upload the source maps during build step const SentryWebpackPlugin = require('@sentry/webpack-plugin') const { @@ -23,7 +19,8 @@ const COMMIT_SHA = process.env.SENTRY_DSN = SENTRY_DSN const basePath = '' -module.exports = withSourceMaps({ +module.exports = { + productionBrowserSourceMaps: true, env: { // Make the COMMIT_SHA available to the client so that Sentry events can be // marked for the release they belong to. It may be undefined if running @@ -85,4 +82,4 @@ module.exports = withSourceMaps({ return config }, basePath, -}) +}