Dev Tools · 2h ago
Developer ditches tailwind-merge after silent class conflict bugs
A developer removed tailwind-merge from seven apps after discovering it silently dropped custom utility classes like 'border-grid' due to heuristic conflicts. The tool resolves class order at runtime, but the author argues conflicts are static and should be caught at build time. They replaced it with a build-time checker and a 25-line concatenation helper.
Meridian48 take
The critique is valid for custom utilities, but tailwind-merge remains essential for large component libraries where variant conflicts are dynamic; the author's solution trades runtime safety for build-time discipline.
tailwind-mergecss-class-conflicts