[Snyk] Upgrade tailwind-merge from 1.8.0 to 1.14.0 #23
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 was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade tailwind-merge from 1.8.0 to 1.14.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: tailwind-merge
New Features
mt-[calc(theme(fontSize.4xl)/1.125)]
would not be recognized correctly because no length unit is present in the arbitrary value.calc()
,min()
,max()
andclamp()
function is used in the arbitrary value.mt-[…]
the arbitrary value can only be a length, so I don't check for it. A consequence of this is that if you use non-Tailwind classes likemt-[this-is-totally-not-tailwind]
, tailwind-merge will recognize it as a Tailwind class from now on. Please don't use classes that look like Tailwind classes with arbitrary value but aren't Tailwind classes with tailwind-merge (in default config) to prevent incorrect merging behavior.Bug Fixes
col-span-full
class missing in default config by @ dcastil in #267Documentation
Full Changelog: v1.13.2...v1.14.0
Bug Fixes
moduleResolution: node16
by @ LiamMartens in #245Documentation
Full Changelog: v1.13.1...v1.13.2
Thanks to @ bluetch for sponsoring tailwind-merge! ❤️
Bug Fixes
basis-auto
andbasis-full
not being merged correctly by @ lukasz-kapica in #242Full Changelog: v1.13.0...v1.13.1
This release focuses on improvements to the docs.
Bug Fixes
0
without unit not being recognized by @ dcastil in #237Documentation
Other
Full Changelog: v1.12.0...v1.13.0
With this release tailwind-merge supports all features introduced in Tailwind CSS v3.3.
New Features
line-height
modifiers infont-size
utilities liketext-lg/7
and more potential postfix modifiers in the future (learn more).w-1/2
which doesn't contain a modifier. So tailwind-merge always checks whether class without potential modifier exists and if it doesn't it checks for full class. This behavior might get reversed in the next major version as a breaking change (learn more).conflictingClassGroupModifiers
object to tailwind-merge config (learn more).Full Changelog: v1.11.0...v1.12.0
New Features
text-lg/7
) introduced in Tailwind CSS v3.3 is not yet supported in tailwind-merge because that feature is a bit more involved. I'll add support for it in a future release. More info in #211.isPercent
which is needed internally for the default scale of color stop positions.gradientColorStopPositions
supported in tailwind-merge.ps-0
(padding-inline-start: 0px;
) are de-duplicated away when using the matching property for all sides afterwards like in this casep-0
, but not when using single axis sides likepx-0
becausepadding-inline-start
can also be the top or bottom padding depending on writing mode.twMerge('ps-0 p-0') === 'p-0' && twMerge('ps-0 px-0') === 'ps-0 px-0'
.Full Changelog: v1.10.0...v1.11.0
Thanks to @ brandonmcconnell for sponsoring tailwind-merge! ❤️
New Features
Full Changelog: v1.9.1...v1.10.0
Bug Fixes
opacity-50 opacity-[.025]
weren't merged correctly. You might not have noticed since classes with arbitrary values are defined after the default ones in the output stylesheet, but merging it the other way around (opacity-[.025] opacity-50
) would have led to a styling bug.isNumber
.Full Changelog: v1.9.0...v1.9.1
New Features
Documentation
Other
Full Changelog: v1.8.1...v1.9.0
Bug Fixes
Full Changelog: v1.8.0...v1.8.1
Thanks to @ aniravi24 for sponsoring tailwind-merge! ❤️
Commit messages
Package name: tailwind-merge
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs