Why using "clsx" ?

[AbdullahSoomroOfficial]

tailwind-merge uses twJoin to join class strings together, ensuring there are no conflicting classes. This means that twMerge already handles class merging efficiently by utilizing twJoin.

Given this, why would we use twMerge(clsx()), which essentially performs the class joining task twice? Wouldn't using clsx alongside twMerge be redundant?

twJoin has the same performance characteristics as other class joining libraries like clsx

[QuentinFrc]

As mentioned in tailwind-merge doc here, twJoin doesn't support object arguments (for this reason).

So clsx is only here to handle object arguments in cn function.

If you never pass objects in cn(...args), for sure you can remove clsx

[AbdullahSoomroOfficial]

Thank you @QuentinFrc for the guidance. 🙏