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
stabilize experimental.enablePrerenderSourcemaps (#84916)
As part of stabilizing cacheComponents, we are also stabilizing
supporting flags. This flag has been enabled with cacheComponents for
some time and so we are moving it out of experimental.
It will continue to be enabled by default if you are using
cacheComponents. Otherwise, it can be opted into independently via next
config.
Closes https://linear.app/vercel/issue/NDX-1048Closes#80317
---------
Co-authored-by: Sebastian "Sebbie" Silbermann <[email protected]>
Copy file name to clipboardExpand all lines: docs/01-app/02-guides/memory-usage.mdx
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,6 +125,10 @@ Generating source maps consumes extra memory during the build process.
125
125
126
126
You can disable source map generation by adding `productionBrowserSourceMaps: false` and `experimental.serverSourceMaps: false` to your Next.js configuration.
127
127
128
+
When using the `experimental.cacheComponents` feature, Next.js will use source maps by default during the prerender phase of `next build`.
129
+
If you consistently encounter memory issues during that phase (after "Generating static pages"),
130
+
you can try disabling source maps in that phase by adding `enablePrerenderSourceMaps: false` to your Next.js configuration.
131
+
128
132
> **Good to know**: Some plugins may turn on source maps and may require custom configuration to disable.
0 commit comments