cn VS tailwind-merge

not sure about the status of the 'Ceph Nano' project, but the goal was to serve ceph S3 from a single container: https://github.com/ceph/cn

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.