New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency purgecss-webpack-plugin to v4 - autoclosed #404
Closed
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
renovate
bot
force-pushed
the
renovate/purgecss-webpack-plugin-4.x
branch
2 times, most recently
from
February 8, 2021 20:53
ca916c8
to
6f90b23
Compare
renovate
bot
force-pushed
the
renovate/purgecss-webpack-plugin-4.x
branch
from
February 21, 2021 13:27
6f90b23
to
474b16d
Compare
renovate
bot
force-pushed
the
renovate/purgecss-webpack-plugin-4.x
branch
from
March 20, 2021 23:20
474b16d
to
7e13485
Compare
renovate
bot
force-pushed
the
renovate/purgecss-webpack-plugin-4.x
branch
from
May 9, 2021 22:54
7e13485
to
26a19f3
Compare
renovate
bot
force-pushed
the
renovate/purgecss-webpack-plugin-4.x
branch
2 times, most recently
from
May 22, 2021 05:32
e89fd15
to
16470e5
Compare
renovate
bot
force-pushed
the
renovate/purgecss-webpack-plugin-4.x
branch
from
May 29, 2021 05:02
16470e5
to
2737fb1
Compare
renovate
bot
force-pushed
the
renovate/purgecss-webpack-plugin-4.x
branch
21 times, most recently
from
June 8, 2021 12:38
0dbcfcc
to
8f18450
Compare
renovate
bot
force-pushed
the
renovate/purgecss-webpack-plugin-4.x
branch
6 times, most recently
from
June 15, 2021 07:44
a8876bf
to
b411799
Compare
renovate
bot
force-pushed
the
renovate/purgecss-webpack-plugin-4.x
branch
3 times, most recently
from
June 21, 2021 21:05
60577ad
to
dc37013
Compare
renovate
bot
force-pushed
the
renovate/purgecss-webpack-plugin-4.x
branch
2 times, most recently
from
June 28, 2021 07:32
200e8d3
to
4651723
Compare
Codecov Report
@@ Coverage Diff @@
## master #404 +/- ##
=======================================
Coverage 60.36% 60.36%
=======================================
Files 44 44
Lines 767 767
Branches 130 130
=======================================
Hits 463 463
Misses 294 294
Partials 10 10 Continue to review full report at Codecov.
|
renovate
bot
force-pushed
the
renovate/purgecss-webpack-plugin-4.x
branch
from
July 5, 2021 07:48
4651723
to
abca7df
Compare
renovate
bot
force-pushed
the
renovate/purgecss-webpack-plugin-4.x
branch
from
July 6, 2021 18:51
abca7df
to
e425d64
Compare
renovate
bot
changed the title
chore(deps): update dependency purgecss-webpack-plugin to v4
chore(deps): update dependency purgecss-webpack-plugin to v4 - autoclosed
Jul 7, 2021
snglth
pushed a commit
to Abstract-Tech/community-theme-profile
that referenced
this pull request
Jul 12, 2023
As part of making the new courseware experience the default for staff, the LMS /jump_to/ links that are exposed by the Course Blocks API via the `lms_web_url` field will soon direct users to whichever experience is active to them (instead of always directing to the legacy experience & relying on the learner redirect). Because of this, the MFE can no longer rely on `lms_web_url` to land a staff user to the legacy experience. However, the aformentioned change will also introduce a `legacy_web_url` field to the API, which we *can* use for this purpose. TNL-7796
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.
This PR contains the following updates:
1.6.0
->4.0.3
Release Notes
FullHuman/purgecss
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.2
Compare Source
v3.1.1
Compare Source
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 FullHuman/purgecss#424
keyframes can be used to add keyframes to the safelist, when using keyframes: true (FullHuman/purgecss#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
Compare Source
Changes:
variables
option to remove unused CSS variablesv2.0.4
Compare Source
v2.0.3
Compare Source
Configuration
📅 Schedule: "before 3am on Monday" in timezone America/New_York.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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 WhiteSource Renovate. View repository job log here.