UNPKG

next

Version:

The React Framework

49 lines (35 loc) • 2.14 kB
--- title: enablePrerenderSourceMaps description: Enable source maps for errors during prerendering in next build. related: links: - app/guides/memory-usage - app/api-reference/config/next-config-js/productionBrowserSourceMaps --- The `enablePrerenderSourceMaps` option lets Node.js use existing source maps during the prerender phase of `next build`. When source maps are available, error stack traces point to the original source code. It defaults to `true`. This option does not generate source maps. Webpack does not generate server source maps by default. To generate them when investigating prerender errors, use [`next build --debug-prerender`](/docs/app/api-reference/cli/next#debugging-prerender-errors). To disable it, set `enablePrerenderSourceMaps` to `false`: ```ts filename="next.config.ts" switcher highlight={4} import type { NextConfig } from 'next' const nextConfig: NextConfig = { enablePrerenderSourceMaps: false, } export default nextConfig ``` ```js filename="next.config.js" switcher highlight={3} /** @type {import('next').NextConfig} */ const nextConfig = { enablePrerenderSourceMaps: false, } module.exports = nextConfig ``` ## Reference | Option | Type | Default | | --------------------------- | --------- | ------- | | `enablePrerenderSourceMaps` | `boolean` | `true` | Disabling source maps during prerendering can reduce [build memory usage](/docs/app/guides/memory-usage#disable-source-maps), but makes prerendering errors harder to debug. ## Version History | Version | Changes | | --------- | ------------------------------------------------------------------------------------------------------------------------------------ | | `v16.3.0` | The default changed to `true`, regardless of whether `cacheComponents` is enabled. | | `v16.0.0` | `enablePrerenderSourceMaps` moved from `experimental.enablePrerenderSourceMaps` to the top-level `enablePrerenderSourceMaps` option. |