From 06b3e5b56ec9f6197e9733ff390cca1981178def Mon Sep 17 00:00:00 2001 From: Charly Gomez Date: Wed, 11 Dec 2024 15:14:56 +0100 Subject: [PATCH] Update docs/platforms/javascript/common/troubleshooting/index.mdx Co-authored-by: Luca Forstner --- docs/platforms/javascript/common/troubleshooting/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/javascript/common/troubleshooting/index.mdx b/docs/platforms/javascript/common/troubleshooting/index.mdx index 3e51db8245295..7ecb83ecf06cf 100644 --- a/docs/platforms/javascript/common/troubleshooting/index.mdx +++ b/docs/platforms/javascript/common/troubleshooting/index.mdx @@ -549,7 +549,7 @@ shamefully-hoist=true The problem is related to memory consumption during the build process, especially when generating source maps. Here are some potential solutions and workarounds: - Update your `@sentry/nextjs` package to the latest version. - - Increase Node.js memory limit: You can try increasing the memory limit for Node.js during the build process. Add this to your build command: `NODE_OPTIONS="--max-old-space-size=4096" next build` + - Increase Node.js memory limit: You can try increasing the memory limit for Node.js during the build process. Add this to your build command: `NODE_OPTIONS="--max-old-space-size=8192" next build`. This flag will increase the memory available to the node process to 8 GB. We have found that Next.js consumes around 4 GB in most cases. Decrease the size depending on your memory availability. - Disable source maps entirely: As a last resort, you can disable source map generation completely: ```js {filename:next.config.js} module.exports = withSentryConfig(module.exports, {