Add support for Tailwind CSS v4.1 #565
Merged
Conversation
This file contains hidden or 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
github-actions
bot
added
feature
Metrics reportAt head commit 442502d and base commit b7527c4 at Size
All size metrics
|
CodSpeed Performance ReportMerging #565 will degrade performances by 15.2%Comparing Summary
Benchmarks breakdown
|
…repeat` and `mask-type` utilities
I also loosened the rules on position vs. origin a bit and allow classes like `*-top-left` and `*-left-top` everywhere. The reason for this is that Tailwind used one style in some groups and another style in others in the past, but moved to support the same order in all groups while keeping the old style working. That means some class groups allow both styles and some not: - object-position: supports both - background-position: supports both - mask-position: Y direction first only - perspective-origin: Y direction first only - transform-origin: Y direction first only To make things simpler and keep the bundle size of tailwind-merge small, I decided to support both styles everywhere.
This is very verbose, but I intend to optimize this later
In the Tailwind CSS codebase it's belonging to position. I don't know why I had it under size.
…er-color groups missing
This reverts commit fedad41. The reverted commit reduced increased `twMerge` bundle size from +7.4% to +5.9% but at the same time made init runtime perf a lot worse from -15.13% to -51.44%
…ha>`, and `text-shadow-*/<alpha>` utilities to control shadow opacity Already supported, only adding test case
…-{left,right}` utilities
|
This was addressed in release v3.2.0. |
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.
Closes #556