next.js
e4c838c1 - Add `--debug-prerender` option for `next build` (#80667)

Commit
260 days ago
Add `--debug-prerender` option for `next build` (#80667) When running `next build --debug-prerender`, we will set a few experimental flags that ensure the following: - No minification is applied to server code. - `experimental.serverMinification = false`, or - `experimental.turbopackMinify = false` - Source maps for server bundles are generated. - `experimental.serverSourceMaps = true` - Source maps are consumed by Node.js in the spawned child processes that prerender the routes. - `experimental.enablePrerenderSourceMaps = true` - The build is not exited after the first error to show a complete list of prerender errors. - `experimental.prerenderEarlyExit = false` While `next dev` remains the primary recommended way to debug prerender errors when `dynamicIO` is enabled, this build option does offer an alternative to get a more usable build output, with readable stacks and code frames. **Note:** For performance reasons, artifacts generated with `next build --debug-prerender` should not be deployed to production. This mode is only intended for debugging purposes. Closes NAR-142
Author
Parents
Loading