fix(deps): update dependency tailwind-merge to v2 #45
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
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.
This PR contains the following updates:
^1.14.0->^2.0.0Release Notes
dcastil/tailwind-merge (tailwind-merge)
v2.0.0Compare Source
The tailwind-merge v2 release has been sitting here almost finished for 2 months already. But the timing was never quite right, especially thinking about the increased support needed after the release. In the meantime, the product of the company I work at launched in public beta and I married. Thank you for your patience.
This release focuses on making it easier to configure the library for new users. Check out the migration guide and if you have any questions, feel free to create an issue.
Breaking Changes
background-imageandbackground-positionbeing merged incorrectly by @dcastil in https://github.com/dcastil/tailwind-merge/pull/300background-positionandbackground-sizecan look very similar and Tailwind CSS uses the samebg-prefix for both groups. This results in some limitations for tailwind-merge.extendTailwindMergeby @dcastil in https://github.com/dcastil/tailwind-merge/pull/294conflictingClassGroupModifiersin config non-optional by @dcastil in https://github.com/dcastil/tailwind-merge/pull/291modulefield from package.json by @dcastil in https://github.com/dcastil/tailwind-merge/pull/289New Features
extendTailwindMergeby @dcastil in https://github.com/dcastil/tailwind-merge/pull/294conflictingClassGroupModifiersin config non-optional by @dcastil in https://github.com/dcastil/tailwind-merge/pull/291modulefield from package.json by @dcastil in https://github.com/dcastil/tailwind-merge/pull/289Bug Fixes
background-imageandbackground-positionbeing merged incorrectly by @dcastil in https://github.com/dcastil/tailwind-merge/pull/300truefor empty strings by @dcastil in https://github.com/dcastil/tailwind-merge/pull/295Documentation
bg-sizeandbg-positionclass groups in docs by @dcastil in https://github.com/dcastil/tailwind-merge/pull/328Full Changelog: dcastil/tailwind-merge@v1.14.0...v2.0.0
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.
This PR has been generated by Mend Renovate. View repository job log here.