Skip to content

Update tailwind-merge 1.8.0 → 1.14.0 (minor)#707

Open
depfu[bot] wants to merge 1 commit into
mainfrom
depfu/update/yarn/tailwind-merge-1.14.0
Open

Update tailwind-merge 1.8.0 → 1.14.0 (minor)#707
depfu[bot] wants to merge 1 commit into
mainfrom
depfu/update/yarn/tailwind-merge-1.14.0

Conversation

@depfu

@depfu depfu Bot commented Jul 17, 2023

Copy link
Copy Markdown
Contributor

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ tailwind-merge (1.8.0 → 1.14.0) · Repo

Release Notes

1.14.0

New Features

  • Improve support for arbitrary values by @dcastil in #263
    • Previously, tailwind-merge checked the content of the arbitrary value portion of a class in most cases to understand whether the type of the arbitrary value is correct (e.g. it checked for number followed by length unit for the length type). That lead to the issue that a class like mt-[calc(theme(fontSize.4xl)/1.125)] would not be recognized correctly because no length unit is present in the arbitrary value.
    • I changed the check of the arbitrary value to also pass when a calc(), min(), max() and clamp() function is used in the arbitrary value.
    • In ambiguous cases, you can use data type labels to mark the type of a class. Read more
    • Moreover, I removed the check where the type of the arbitrary value is unambiguous. In the class 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 like mt-[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

  • Fix col-span-full class missing in default config by @dcastil in #267
  • Fix arbitrary value with no present length unit not being recognized by @dcastil in #263

Documentation

  • Add missing info about where to call config functions to docs by @dcastil in #264

Full Changelog: v1.13.2...v1.14.0

1.13.2

Bug Fixes

Other

Full Changelog: v1.13.1...v1.13.2

Thanks to @bluetch for sponsoring tailwind-merge! ❤️

1.13.1

Bug Fixes

Full Changelog: v1.13.0...v1.13.1

1.13.0

This release focuses on improvements to the docs.

New Features

  • Add intro video from Simon Vrachliotis to docs by @dcastil in #239
    • @simonswiss made an intro video to tailwind-merge which I added to the docs. Check it out here!
  • Add docs about when to use tailwind-merge by @dcastil in #230
    • I added a new page to the docs about when and how to use tailwind-merge which should help you to decide whether you should use it and what alternative approaches exist.
  • Make it clearer in docs that tailwind-merge supports composition of class strings by @dcastil in #229
  • Add npm package provenance by @dcastil in #219
    • GitHub introduced a new security feature to verify which source commit and build file were used for a specific npm package version. tailwind-merge now publishes provenance signatures alongside all releases on npm. Read more on the GitHub blog.

Bug Fixes

Full Changelog: v1.12.0...v1.13.0

1.12.0

With this release tailwind-merge supports all features introduced in Tailwind CSS v3.3.

New Features

  • Add support for postfix modifier by @dcastil in #214
    • This adds support for line-height modifiers in font-size utilities like text-lg/7 and more potential postfix modifiers in the future (learn more).
    • All classes are checked for postfix modifiers since there will be more in the future and they'll be configurable with plugins.
    • tailwind-merge can't know from the class syntax alone whether something is a modifier or not. E.g. there is 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).
    • Added conflictingClassGroupModifiers object to tailwind-merge config (learn more).

Full Changelog: v1.11.0...v1.12.0

1.11.0

New Features

  • Add support for Tailwind CSS v3.3 except line-height shorthand by @dcastil in #210
    • The line-height shorthand in font-size utilities (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.
    • Added new validator isPercent which is needed internally for the default scale of color stop positions.
    • New theme key gradientColorStopPositions supported in tailwind-merge.
    • New logical properties like ps-0 (padding-inline-start: 0px;) are de-duplicated away when using the matching property for all sides afterwards like in this case p-0, but not when using single axis sides like px-0 because padding-inline-start can also be the top or bottom padding depending on writing mode.
      • Basically twMerge('ps-0 p-0') === 'p-0' && twMerge('ps-0 px-0') === 'ps-0 px-0'.
      • If you want to use logical properties and know which writing modes your app is limited to, add the right conflicts yourself to your tailwind-merge config.

Full Changelog: v1.10.0...v1.11.0

Thanks to @brandonmcconnell for sponsoring tailwind-merge! ❤️

1.10.0

New Features

  • Add support for container query length units in arbitrary values by @LesnoyPudge in #204

Full Changelog: v1.9.1...v1.10.0

1.9.1

Bug Fixes

  • Fix arbitrary floats not supported in opacity, scale, etc. by @dcastil in #196
    • Up until now classes like 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.
    • This fix led to a new validator isNumber.
  • Fix arbitrary border color value being merged incorrectly by @dcastil in #195

Full Changelog: v1.9.0...v1.9.1

1.9.0

New Features

Bug Fixes

Other

Full Changelog: v1.8.1...v1.9.0

1.8.1

Bug Fixes

  • Fix incorrect class group conflicts in grid-related classes by @dcastil in #177

Full Changelog: v1.8.0...v1.8.1

Thanks to @aniravi24 for sponsoring tailwind-merge! ❤️

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@vercel

vercel Bot commented Jul 17, 2023 •
edited
Loading

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
ronz-nextjs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 17, 2023 4:43pm

@depfu depfu Bot added the depfu label Jul 17, 2023
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 17, 2023 •
edited
Loading

Copy link
Copy Markdown

Deploying with  Cloudflare Pages  Cloudflare Pages

Latest commit: 51cfc58
Status:🚫  Build failed.

View logs

@depfu depfu Bot assigned LordRonz Jul 17, 2023
@depfu
depfu Bot requested a review from LordRonz July 17, 2023 16:42
@sonarqubecloud

sonarqubecloud Bot commented Jul 17, 2023

Copy link
Copy Markdown

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@depfu depfu Bot mentioned this pull request Jul 17, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@LordRonz LordRonz Awaiting requested review from LordRonz

Assignees

@LordRonz LordRonz

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@LordRonz