Replies: 1 comment
-
Just a clarification here, so you run the export "in parallel/concurrently", and they all collide at the build step, is that right? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
1.Support custom distDir
Non-Goals
Background
Due to some company business requirements, I need to use multi-process builds in development and use static exports. However, when setting output to export, the build directory will be forced to be changed to .next, which will cause the same directory operation and thus cause the build to fail. When I modified the next.js source code to support custom build directories, I can correctly implement multi-process builds and exports.
Proposal
modify the "configOutDir" and ajust the function "hasCustomExportOutput"
Beta Was this translation helpful? Give feedback.
All reactions