You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am really looking forward to Tailwind v4. I plan to start experimenting with it soon.
I'm here today to ask if there's anything that can be done to facilitate the transition to third-party modules like tailwind-merge (dcastil/tailwind-merge#468).
This library is super useful for component libraries and overrides.
To give you more context:
I have built a library called Tailwind Buddy (https://github.com/busbud/tailwind-buddy), which is similar to Class Variant Authority and Tailwind Variant but faster. It's designed to build component functions that also handle responsiveness.
In cases of compound conditions or even className overrides from outside of the component, we don't want to keep HTML classes that we don't use. I know Tailwind, at least in v3, was smart enough to put the classes from left to right in the correct order as there are no specificities.
Another question: Wouldn't it be super useful to integrate a library like tailwind-merge directly into the Tailwind library or facilitate its use, as it's really useful for component library maintainers?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am really looking forward to Tailwind v4. I plan to start experimenting with it soon.
I'm here today to ask if there's anything that can be done to facilitate the transition to third-party modules like tailwind-merge (dcastil/tailwind-merge#468).
This library is super useful for component libraries and overrides.
To give you more context:
Thank you for your time and your work!
Beta Was this translation helpful? Give feedback.
All reactions