feat(schema): split dev/prod build directories#28594
Merged
Conversation
|
|
pi0
reviewed
Aug 19, 2024
pi0
approved these changes
Aug 19, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
#14607
📚 Description
This adds support for splitting dev + production build directories. Because type-support is based on having a
.nuxt/tsconfig.jsonin place, we can't always split out the build directory.I've opted to use
buildIdfor the production build directory to allow parallel production builds - but this implementation detail will likely change when we implement #23392 (next on the list!)This should enable running parallel builds alongside a dev server (or even multiple builds in parallel at the same time).
Next steps
nuxishould run prepare step on a separate directory before building (?)