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
There are some uses cases that are too custom for tailwind-merge to handle but that would benefit from leveraging tailwind-merge's understanding of Tailwind CSS classes and conflicts between them.
So far I'm thinking of a new exported function like createTailwindMergeUtils or extendTailwindMergeUtils or so that exports a bunch of util functions to get all the information that tailwind-merge uses internally.
There are some uses cases that are too custom for tailwind-merge to handle but that would benefit from leveraging tailwind-merge's understanding of Tailwind CSS classes and conflicts between them.
Two example use cases:
tailwind-merge could expose a low-level API that makes it possible to use its internal logic for those use cases.
Some important aspects this feature must fulfill:
The text was updated successfully, but these errors were encountered: