Exclude assets from other plugin instances #2182
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.
R: @philipwalton
Fixes #2181
The one thing that makes me a little uneasy about this is that it relies on static, module-scoped state to keep track of the assets output by other instances of the exported class. I think it's appropriate for this use case, but at the same time, I kind of wish there were another viable approach—like a sanctioned way of adding state to the webpack
compilation
object, but I can't find references to anyone doing that, so I assume it would be even hacky-er.