Update dependency @fullhuman/postcss-purgecss to v5 #285
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 PR contains the following updates:
1.3.0
->5.0.0
Release Notes
FullHuman/purgecss (@fullhuman/postcss-purgecss)
v5.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
v4.1.3
Compare Source
v4.1.2
Compare Source
v4.1.1
Compare Source
v4.1.0
Compare Source
Bug Fixes
Features
v4.0.3
Compare Source
Features
v4.0.2
Compare Source
v4.0.1
Compare Source
Bug Fixes
Features
v4.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
Drop PostCSS 7 support, use @fullhuman/postcss-purgecss 3.0 with PostCSS 7.
v3.1.3
Compare Source
Changes
Bug Fixes
v3.1.0
Compare Source
v3.0.0
Compare Source
3.0.0
Simplifying whitelist option
Whitelist started as a simple option named
whitelist
but grew up with the different use-cases and needs that appear with time. Another option calledwhitelistPatterns
appeared, thenwhitelistPatternsChildren
, …It is now more complex and complicated, and somewhat difficult to remember how to use it with different options.
To summarize the changes, the whitelist options are now grouped in one option called safelist. And the most used options can be defined in one array.
Two forms are available. The simple form is:
In this form, safelist is an array that can take a string or a regex.
The complex form is:
In this form, safelist is an object taking optional properties:
standard is the same as the simple form and replaces
whitelist
and whitelistPatternsdeep replaces whitelistPatternsChildren
greedy is a new option coming from https://github.com/FullHuman/purgecss/pull/424
keyframes can be used to add keyframes to the safelist, when using keyframes: true (https://github.com/FullHuman/purgecss/issues/418)
variables can be used to add CSS variables to the safelist, when using variables: true
New Option: Blocklist
Blocklist will block the CSS selectors from appearing in the final output CSS. The selectors will be removed even when they are seen as used by PurgeCSS.
Even if
nav-links
andusedClass
are found in your content files (HTML, Javascript), they will be removed.CLI
PurgeCSS is using commander.js for its CLI. The recent version of commander.js introduced the possibility of making an option variadic. This means when specifying multiple option arguments, the parsed option value will be an array.
A few options are now taking advantage of this new feature: content, css, and the newly introduced option safelist and blocklist. It is no longer necessary to separate the list items with a comma.
From changelog:
v2.3.0
Compare Source
v2.2.0
Compare Source
v2.1.2
Compare Source
v2.1.0
Compare Source
v2.0.6
Compare Source
v2.0.5
: v2.0Compare Source
Changes:
variables
option to remove unused CSS variablesv2.0.4
Compare Source
v2.0.3
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.