cva VS tailwind-merge

cva.style

* use cva https://github.com/joe-bell/cva to style generic ui components (like buttons) to archive same grouping as in semantic css

Highly recommended with this: https://github.com/joe-bell/cva

Yes, and a library like https://github.com/joe-bell/cva makes this a breeze. See https://cva.style/docs/getting-started#your-first-component for an example

There is also class variance authoriy

https://github.com/joe-bell/cva is great for this

Also have you heard of class variance authority? https://github.com/joe-bell/cva; personally looked into stitches & vanilla-extract but i'm preferring the simplicity of this package the most.

So the library I use is tailwind-merge, which is a class that eliminates conflicts between classes when using Tailwind. So I created the following utility function.

clsx is a tiny utility for constructing className strings conditionally, I use it in conjunction with tailwind-merge which merges Tailwind CSS classes without style conflicts.

I searched for a solution, and I found tailwind-merge which is written in JavaScript. Basically it finds conflicted classes and resolve the conflict. For example:

I would suggest you to use CVA and tailwind-merge.

Hey everyone! I built an open source library called tailwind-merge which helps with resolving style conflicts in CSS class strings. → https://github.com/dcastil/tailwind-merge

I used tailwind-merge and cva to build my UI component library Rewind-UI.

I use Tailwind + Next.js on most of my projects. Usually I add the following to the mix: - RadixUI+ tailwindcss-radix or HeadlessUI although I like Radix more - classnames - https://tailwindcss.com/blog/automatic-class-sorting-with-prettier - tailwind-merge - CSS Modules

I'm using Tailwind CSS and I'd like to integrate a library called tailwind-merge into my Vue app. I'd like the plugin to replace Vue's class appending behavior so that all components in my app have their Tailwind utility classes merged to prevent style conflicts. It may not be everyone's preferred solution to such a problem, but I think it's a very valid use cases for this sort of thing.