Retain steal configuration from previous bundles #219
Merged
Conversation
This file contains 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
When steal-tools runs its build it loads each bundle separately a new loader like so: - a - b - c If `b` has some configuration needed for its production bundle and `c` runs through without that configuration, that configuration will be omited. This fixes it so that each time we load a new bundle we use the previous bundles configuration as a starting point. Closes #216
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.
When steal-tools runs its build it loads each bundle separately a new
loader like so:
If
bhas some configuration needed for its production bundle andcruns through without that configuration, that configuration will be
omited.
This fixes it so that each time we load a new bundle we use the previous
bundles configuration as a starting point.
Closes #216