feat: support multiple build configs #275
Merged
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.
closes #245
There are no breaking changes, and no action is required on the upgrade.
This change allows to have multiple build configurations in
unbuild.config
file. This is very much needed if you have different entry points and want separate flows for them or even a single entry point but a few different outcomes.so basically you can do:
or still do
Short description of changes:
build
command has been extracted to read multiple configurations. These configurations are merged the same way they were and run one after another, with the rest of the code moved to an internalsingleConfigBuild
build. This way API of the package is not changing