Regarding classes in React, we get a lot of power out of the box.
However, we can enhance this power to make it even better.
We can leverage the c...
For further actions, you may consider blocking this person and/or reporting abuse
I see the use case for this, but personally I do it by creating a
classnamevariable in the logic portion of my component rather than the jsx.I think it's very unlikely I'd need to use more than one custom class name to a component.
Mainly comes in handy for me when using dynamic classnames (if x then y else z) kind of thing.
What are the differences between classnames and clsx?
I don't know clsx, probably the same kind of thing.
There are tons of these packages out there, all claim to be better/faster/more unique.
With this stuff to me it makes little to no difference if one is faster, as it will get compiled eventually.
clsx is more better
npmtrends.com/classnames-vs-clsx
Not sure where it's better in this page?
Would you mind elaborating on that?
Simple just compare package size
I wrote classd to resolve classnames using template literals. Also it's faster than classnames in most cases. npmjs.com/package/classd
Hands down one of the most useful packages i've stumbled upon.
I like the bind option, but I tend to use template literals to handle my class name logic for my projects. Provided you've got prettier configured right it shouldn't end up looking messy
For simple concats binding with template literals is my preferred way as well.
For conditional classes I prefer this as you can split it up more easily.
Great tool! But I would rather compose these class names myself. No need to add some extra KBs to my app size 😄
Been using
classnamesfor the past 5 years every week, can't imagine developing without it. Good post!