Files
vercel__next.js/errors/parallel-build-without-worker.mdx
Jam Balaya e5ce54de0b docs: use relative urls (#72941)
## Description
Follow up #52038.
Remove `https://nextjs.org` from URL in [error
pages](https://github.com/vercel/next.js/tree/canary/errors).

### Improving Documentation

- [x] Run `pnpm prettier-fix` to fix formatting issues before opening
the PR.
- [x] Read the Docs Contribution Guide to ensure your contribution
follows the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

---------

Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com>
2024-11-19 08:58:29 +00:00

19 lines
793 B
Plaintext

---
title: Parallel Build Without Build Worker
---
## Why This Error Occurred
The `experimental.parallelServerCompiles` and `experimental.parallelServerBuildTraces`
options require that the `experimental.webpackBuildWorker` option is set to `true`. These
options use workers to improve the parallelization of the build which may improve performance,
but the build may use more memory at the same time.
## Possible Ways to Fix It
Build workers are enabled by default unless you have a custom webpack config. You can force enable the option by setting `experimental.webpackBuildWorker: true` in your `next.config.js` file, but some webpack configuration options may not be compatible.
## Useful Links
- [Webpack Build Worker automatic opt-out](/docs/messages/webpack-build-worker-opt-out)