V1 not compatible with TailwindCSS 3.x due to tailwind-merge version bump

[jaydiablo]

We upgraded tailwind-variants to the 1.0 release (and subsequently bumped tailwind-merge to match the dependency defined, which is 3.0.x) and discovered that conflicting classes weren't being removed as they were previous to the upgrade.

In tailwind-merge's README it mentions that if you're using Tailwind 3.x, to stay on the 2.x version:

Perhaps it's worth mentioning this in the README of this project, or in the documentation site?

[jrgarciadev]

@winchesHe please clarify this on the docs

[fredericDelaporte]

tailwind-variants v2 has no more an explicit dependency on tailwind-merge, so I hoped it would resolved this issue. That is not the case, because it still does have it as an optional dependency >=3.0.0. So, attempting to install tailwind-merge v2.6.0 along tailwind-variant v2.0.1 fails.

So, it seems tailwind-variants 1.0.0 breaks the support of the merge feature for Tailwing v3 users. Can this be documented or fixed please?