a dedupe version?
- LU
Hey, I don't think so 馃檲 While it's certainly easy to implement, I've not actually seen a need for this in apps. It's also easy to implement yourself the 1 time (out of 500) you might actually need this.
Mostly I want to avoid the complexity of shipping multiple entry points, all with multiple formats... because the one time you or a coworker adds an import to `clsx/dedupe`, you now have two different copies of `clsx` floating around in your bundle.
Hoping I explained that well enough 鈥撀爐he verbal side of my head isn't working today~ Closing for now, Thanks!
- DY
Stumbled upon the same. Dedupe version is actually really useful for cases, when we deal with existing components, not react, where we create component from scratch each time. Eg. that would enable ```js el.classList.value = clsx(...Array.from(el.classList), ...additionalClasses) ```
sherakamareferenced this in ADAPT-000: Bundlers and ESModule Classnames alternative #125 years ago on GitHub
tbradshareferenced this in Resolves #37695 - Use clsx instead of classnames #377082 years ago on GitHub