Replace gulp-clean-css with postcss-cssnano (Case 161784)#30
Draft
polarbirke wants to merge 2 commits intomasterfrom
Draft
Replace gulp-clean-css with postcss-cssnano (Case 161784)#30polarbirke wants to merge 2 commits intomasterfrom
polarbirke wants to merge 2 commits intomasterfrom
Conversation
polarbirke
changed the title
polarbirke
changed the title
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
1 participant
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.
This is a continuation of the problem-solving started in #28 and #29.
gulp-clean-css has probably become stale (with its author completely unresponsive), and while clean-css still is the most downloaded CSS minification package on npm, its author has put the project into "maintenance mode" and will no longer actively work on it.
Addendum June 2025: gulp-clean-css seems to completely remove Cascade Layers
cssnano has an active group of contributors and fits seamlessly into the existing configuration as a postcss plugin.
Downsides:
As it is logical to first purge unused CSS before performing any other transformations on the remaining code, the order of the postcss plugins is adjusted accordingly.