Skip to content
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
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 5, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
purgecss-webpack-plugin (source) 1.6.0 -> 4.0.3 age adoption passing confidence

Release Notes

FullHuman/purgecss

v4.0.3

Compare Source

Features
  • add dynamic attributes option (9b0fdc3), closes #​588
  • add skippedContentGlobs option to webpack and gulp plugin (e3dce1a)

v4.0.2

Compare Source

v4.0.1

Compare Source

Bug Fixes
  • attribute selector with spaces being removed (418dc7e), closes #​392
  • webpack plugin option blocklist types (5b029c2)
Features

v4.0.0

Compare Source

Bug Fixes
  • test: webpack test type error (c41ad27)
Features
BREAKING CHANGES

v3.1.3

Compare Source

Changes
  • postcss-purgecss remove postcss 8 as peer dependency
  • purgecss-webpack-plugin fix backward compatibility with webpack 4
  • PurgeCSS Update to PostCSS 8
  • postcss-purgecss Add compatibility with PostCSS 8
  • purgecss-webpack-plugin Fix deprecation warning with Webpack 5
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 called whitelistPatterns appeared, then whitelistPatternsChildren, …
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:

safelist: ['invisibleClass', /^nav-/]

In this form, safelist is an array that can take a string or a regex.

The complex form is:

safelist: {
 standard: ['invisibleClass', /^nav-/],
 deep: [],
 greedy: [],
 keyframes: [],
 variables: []
}

In this form, safelist is an object taking optional properties:
standard is the same as the simple form and replaces whitelist and whitelistPatterns
deep 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.

blocklist: ['usedClass', /^nav-/]

Even if nav-links and usedClass 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:
  • CLI: add blocklist option (3961afb)
  • add blocklist option (04223f7)
  • add safelist option, replace whitelist
  • add safelist keyframes and css variables (dc59d30), closes #​418 #​439

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:

  • Asynchronous
import PurgeCSS from "purgecss";

const purgecssResults = await new PurgeCSS().purge({
    // options
});
  • Extractor is a function
content => content.match(/[\w-/:]+(?<!:)/g) || []
  • variables option to remove unused CSS variables
  • Drop support of NodeJS < 8

v2.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.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/purgecss-webpack-plugin-4.x branch 2 times, most recently from ca916c8 to 6f90b23 Compare February 8, 2021 20:53
@renovate renovate bot force-pushed the renovate/purgecss-webpack-plugin-4.x branch from 6f90b23 to 474b16d Compare February 21, 2021 13:27
@renovate renovate bot force-pushed the renovate/purgecss-webpack-plugin-4.x branch from 474b16d to 7e13485 Compare March 20, 2021 23:20
@renovate renovate bot force-pushed the renovate/purgecss-webpack-plugin-4.x branch from 7e13485 to 26a19f3 Compare May 9, 2021 22:54
@renovate renovate bot force-pushed the renovate/purgecss-webpack-plugin-4.x branch 2 times, most recently from e89fd15 to 16470e5 Compare May 22, 2021 05:32
@renovate renovate bot force-pushed the renovate/purgecss-webpack-plugin-4.x branch from 16470e5 to 2737fb1 Compare May 29, 2021 05:02
@renovate renovate bot requested a review from a team May 29, 2021 05:02
@renovate renovate bot force-pushed the renovate/purgecss-webpack-plugin-4.x branch 21 times, most recently from 0dbcfcc to 8f18450 Compare June 8, 2021 12:38
@renovate renovate bot force-pushed the renovate/purgecss-webpack-plugin-4.x branch 6 times, most recently from a8876bf to b411799 Compare June 15, 2021 07:44
@renovate renovate bot force-pushed the renovate/purgecss-webpack-plugin-4.x branch 3 times, most recently from 60577ad to dc37013 Compare June 21, 2021 21:05
@renovate renovate bot force-pushed the renovate/purgecss-webpack-plugin-4.x branch 2 times, most recently from 200e8d3 to 4651723 Compare June 28, 2021 07:32
@codecov-commenter
Copy link

codecov-commenter commented Jun 28, 2021

Codecov Report

Merging #404 (e425d64) into master (42d6535) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           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.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 42d6535...e425d64. Read the comment docs.

@renovate renovate bot force-pushed the renovate/purgecss-webpack-plugin-4.x branch from 4651723 to abca7df Compare July 5, 2021 07:48
@renovate renovate bot force-pushed the renovate/purgecss-webpack-plugin-4.x branch from abca7df to e425d64 Compare July 6, 2021 18:51
@renovate 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
@renovate renovate bot closed this Jul 7, 2021
@renovate renovate bot deleted the renovate/purgecss-webpack-plugin-4.x branch July 7, 2021 20:16
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants