You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Sentry Nextjs causes dev server to recompile forever #4115
@sentry/nextjs 6.14.0 causes the Next.js dev server to recompile infinitely. I'm on node 16.8 and nextjs 11.0.1.
Downgrading to @sentry/nextjs 6.13.3 fixes the infinite recompiling (without needing to downgrade other sentry packages).
Reacted by Simon Victory, Julian Meyer, Naoyuki Yamada, Pablo Caballero, Tobias Lundgren, Luke Boyle, Ulysse Tallepied, mehran motiee, Maciej Sykuła, Willian Rodrigues and 14 more
const { withSentryConfig } = require('@sentry/nextjs')
const withImages = require('next-images')
const { i18n } = require('./next-i18next.config')
const { BGD_ENV } = process.env
const basePath = '/checkout'
const SentryWebpackPluginOptions = {
// Additional config options for the Sentry Webpack plugin. Keep in mind that
// the following options are set automatically, and overriding them is not
// recommended:
// urlPrefix: `~${basePath}/_next`,
// release, url, org, project, authToken, configFile, stripPrefix,
// urlPrefix, include, ignore
// For all available options, see:
// https://github.com/getsentry/sentry-webpack-plugin#options.
}
const moduleExports = withImages({
i18n,
experimental: { esmExternals: true },
crossOrigin: 'anonymous',
images: {
disableStaticImages: true,
domains: ['citygross.se']
},
env: {
BGD_ENV
},
basePath
// Make sure adding Sentry options is the last code to run before exporting, to
// ensure that your source maps include changes from all other Webpack plugins
})
module.exports = withSentryConfig(moduleExports, SentryWebpackPluginOptions)
Activity
svict4 commentedon Nov 4, 2021
Also experiencing the same recompile looping, nextjs@v11.1.2.
Downgrading to v6.13.3 also fixed for me.
gish commentedon Nov 4, 2021
Same here, nextjs@v12.0.2
mhase commentedon Nov 4, 2021
tested on next@10.0.8
downgrading to v6.13.3 fixed the issue 👌🏻
willianrod commentedon Nov 4, 2021
Same here with nextjs@v10.2.0. Downgrading @sentry/nextjs to 6.13.3 fixes the problem
sanderkooger commentedon Nov 4, 2021
Same issue here.
AbhiPrasad commentedon Nov 4, 2021
Hey folks, thanks for writing in. Is it possible for anyone to provide a reproduction?
A copy of your
next.config.jswould be a big help as well.sanderkooger commentedon Nov 4, 2021
jonahallibone commentedon Nov 4, 2021
Another examples
Joelgullander commentedon Nov 4, 2021
Same issue here:
adikari commentedon Nov 5, 2021
Upgrading to latest sentry caused it for me too. Downgrading fixes it.
lobsterkatie commentedon Nov 5, 2021
Sorry, everyone! Should be fixed in #4123.
AbhiPrasad commentedon Nov 5, 2021
Fix released as part of https://www.npmjs.com/package/@sentry/nextjs/v/6.14.1, please let us know if there are any other problems!
ulysset commentedon Nov 5, 2021
It works thanks :)
MAfzalKhan1997 commentedon Nov 9, 2021
facing the same on "@sentry/nextjs": "6.14.0" trying to resolve the issue from yesterday but no luck, upgrading to 6.14.1 resolved the issue. ❤
jonioni commentedon Jan 12, 2022
Great fix! Was also suffering from the very same problem in our Next.js project for long, only to find the root cause here (missing
dev)!#4123 should be referenced by anyone who is also doing webpack
isServercheck within theirnext.config.js.Kudos to @lobsterkatie 👍 !