import classNames from "classnames";

imagine installing, importing, and using a package that is solved quite literally by built in parts of the language

yawn

i grow weary

*stares at `is-even` npm package*

Looks like a react issue than javascript one
Insists on being a library instead of framework but it's such an awful dev experience on its own that ppl resort to installing 20 packages to manage basic css/classes

Vanillajs: just modify .class/classList whenever you want to
Vue: :class="{ something: condition }"
Svelte: class:something={condition}
Solidjs: classList={{something: condition}}

And besides being so limited it still manages to be one of the slowest and most bloated ones

@devRancid gtfo clown troll, this has nothing to do with what framework you are using

you'd know that if you weren't a troll

🤡🤡🤡🤡🤡

have fun tinkering around in "pure" HTML for all your projects

Looks like someone got triggered because he has to work with clown software all day 🤡🤡🤡🤡🤡🤡

@devRancid "Just" use this type that is used nowhere else in the entire fucking language and doesn't share the basic array methods.

BTW this is a function I defined in every React project I ever started, in my case it's something like

arguments.filter(x => x).join(" ")

It doesn't look like that because that's the best way to write this function, it looks like that because a better implementation doesn't pay off.

I'll gladly trade that for this package.