Fix compression-webpack-plugin filename option #1121
Merged
+13
−6
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
apaleslimghost
requested review from
ft-dependency-auto-merger and
a team
as code owners
joelcarr
approved these changes
Jan 21, 2025
ivomurrell
approved these changes
Jan 21, 2025
apaleslimghost
force-pushed
the
fix-compression-filename-option
branch
from
0d33cea to
c4212ab
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.
the semantics of the
[path]placeholder changed in version 5 of the plugin, which causesConflict: Multiple assets emit different content to the same filename .gzerrors with a production build.also changes the
ft-uiexample to build in production mode, so we've at least got something that's testing that.