Repository navigation
allow parallel bundles to isolate their css source caches - #57
Merged
Merged
Conversation
|
Thank you, this fixes my problems! |
Member
|
Thanks @loklaan ! |
joshwnj
added a commit
that referenced
this pull request
Nov 19, 2015
allow parallel bundles to isolate their css source caches
Member
|
Published v0.14.0 |
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
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.
I found that if we didn't key the internal source caches in css-modulesify by something identifiable per build pipe (like the expected css output file name), we'd soon find unexpected css scattered across our our screens.
This issue should have only affected larger build setups that need to start several instances of browserify in a single build.