Skip to content

Commit

Permalink
Update docs/platforms/javascript/common/troubleshooting/index.mdx
Browse files Browse the repository at this point in the history
Co-authored-by: Luca Forstner <[email protected]>
  • Loading branch information
chargome and lforst authored Dec 11, 2024
1 parent 9e13e6a commit 06b3e5b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/platforms/javascript/common/troubleshooting/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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, {
Expand Down

0 comments on commit 06b3e5b

Please sign in to comment.