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
The .gap-px utility is not merged with .gap-1 as expected when using tailwind-merge. Instead of resolving to a single gap utility, both classes remain, leading to potential styling conflicts.
To Reproduce
Use tailwind-merge to process a class list that includes both .gap-px and .gap-1.
Observe that both classes persist instead of .gap-1 taking precedence.
Describe the bug
The
.gap-px
utility is not merged with.gap-1
as expected when usingtailwind-merge
. Instead of resolving to a single gap utility, both classes remain, leading to potential styling conflicts.To Reproduce
tailwind-merge
to process a class list that includes both.gap-px
and.gap-1
..gap-1
taking precedence.You can use the following CodeSandbox to reproduce the issue:
https://codesandbox.io/p/sandbox/suspicious-burnell-qx2z9k?file=%2Fsrc%2Findex.ts
Expected behavior
The
.gap-1
utility should replace.gap-px
in the final merged class list since it has a higher numerical value.Environment
tailwind-merge
version: 3.0.1The text was updated successfully, but these errors were encountered: