feat: modify merge config order #135
Merged
Conversation
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
fi3ework
approved these changes
Aug 28, 2024
fi3ework
force-pushed
the
feat/user-config
branch
from
7af0ca1 to
68b51e8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The priorities from high to low are as follows:
userConfig: users can configure any Rsbuild and Rspack configlibRsbuildConfig: the configuration that we compose from Rslib unique config and userConfig from 1internalRsbuildConfig: the built-in best practice Rsbuild configuration we provide in RslibWe should state in the document that the built-in configuration should not be changed optionally
Related Links
Checklist