fix(@angular-devkit/build-angular): enable :where CSS pseudo-class
#22466
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
Currently when using the `:where` CSS pseudo-class in Angular CLI projects, a warning will be emitted, as `:where` could not be interpreted. Updating to the latest version of `critters` fixes this issue. (cherry picked from commit 9a9af20)
dgp1130
added
target: patch
alan-agius4
approved these changes
Jan 10, 2022
|
@dgp1130 Thank you for the manual effort in enabling this 👍 |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Currently when using the :where CSS pseudo-class in Angular CLI projects,
a warning will be emitted, as :where could not be interpreted. Updating
to the latest version of critters fixes this issue.
Refs #22437
This is a manual cherry-pick of #22451 onto the
13.1.xbranch to deal with some merge conflicts.