ca5bc989d1
This PR introduces 2 experimental options for doing more work in the webpack build in parallel instead of in serial. These options may improve the performance of builds at the cost of more memory. `parallelServerAndEdgeCompiles`: This option kicks off the builds for both `server` and `edge-server` at the same time instead of waiting for each to complete before the next one. In applications that have many server and edge functions, this can increase performance by doing that work in parallel. This can be used with `next build` or `next experimental-compile`. `parallelServerBuildTraces`: This option starts the server build traces as soon as the server compile completes and runs it in the background while the other compilations are happening. With this option enabled, some unnecessary work may be done since ordinarily the client compilation provides information that can reduce the amount of tracing necessary. However, since it is in parallel with the other work, it may still result in a faster build in total at the cost of more memory. This option is already the default when using `next experimental-compile` but can now be used when `next build` is used also. --------- Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com> Co-authored-by: JJ Kasper <jj@jjsweb.site> |
||
---|---|---|
.. | ||
app | ||
pages | ||
public | ||
styles | ||
experimental-compile.test.ts | ||
index.test.ts | ||
middleware.js | ||
next.config.js | ||
standalone-gsp.test.ts | ||
standalone.test.ts | ||
useReportWebVitals.test.ts | ||
vercel-speed-insights.test.ts |