fix(deps): update dependency @tailwindcss/postcss7-compat to v2.2.17 #254
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:
2.2.4
->2.2.17
Release Notes
tailwindlabs/tailwindcss (@tailwindcss/postcss7-compat)
v2.2.17
Compare Source
Fixed
awaitWriteFinish
setting to avoid occasional stale builds on Windows (#5758)v2.2.16
Compare Source
Fixed
v2.2.14
Compare Source
Fixed
@defaults
in JIT, switch back toclean-css
in case there's any meaningful differences in the output (bf248cb)v2.2.10
Compare Source
Fixed
presets: []
in config file (#4903)Added
optimizeUniversalDefaults
flag (a9e160c)v2.2.9
Compare Source
Fixed
@apply
ing utilities that contain variants + the important modifier (#4854)clean-css
to v5.1.4 to fix empty CSS variables in CDN builds (#5338)v2.2.8
Compare Source
Fixed
@apply
(#5249)object-position
utilities (#5245)v2.2.7
Compare Source
Fixed
v2.2.6
Compare Source
Fixed
v2.2.5
Compare Source
Added
self-baseline
utility (I know this is a patch release, no one's going to die relax) (#5000)Changed
JIT: Optimize universal selector usage by inlining only the relevant selectors (#4850))
This provides a very significant performance boost on pages with a huge number of DOM nodes, but there's a chance it could be a breaking change in very rare edge cases we haven't thought of. Please open an issue if anything related to shadows, rings, transforms, filters, or backdrop-filters seems to be behaving differently after upgrading.
Fixed
step-start
andstep-end
in animation utilities (#4795))!*
in templates from ruining everything (#4816))@layer
rules being mistakenly inserted during incremental rebuilds (#4853))[hidden]
works as expected on elements where we override the defaultdisplay
value in Preflight (#4873)backdropOpacity
utilities (#4892)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled because a matching PR was automerged previously.
♻ 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 was generated by Mend Renovate. View the repository job log.