Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency tailwind-merge to v1.14.0 #21

Merged
merged 1 commit into from
Jul 21, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 21, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
tailwind-merge 1.13.2 -> 1.14.0 age adoption passing confidence

Release Notes

dcastil/tailwind-merge (tailwind-merge)

v1.14.0

Compare Source

New Features
  • Improve support for arbitrary values by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/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
Documentation

Full Changelog: dcastil/tailwind-merge@v1.13.2...v1.14.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented Jul 21, 2023

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

Name Status Preview Comments Updated (UTC)
todo-app ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 21, 2023 10:40am

@renovate renovate bot force-pushed the renovate/tailwind-merge-1.x-lockfile branch from 5d3a8da to c03b305 Compare July 21, 2023 10:40
@emon5122 emon5122 merged commit c686e4f into main Jul 21, 2023
1 check passed
@emon5122 emon5122 deleted the renovate/tailwind-merge-1.x-lockfile branch July 21, 2023 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant