Gemini Executive Synthesis

`cn`'s class merging logic for arbitrary `font-[...]` values, specifically its differentiation between `font-weight` and `font-family`.

Technical Positioning

Achieving "Full parity" with `tailwind-merge` and correct interpretation of Tailwind v4's CSS class semantics, particularly for arbitrary values.

SaaS Insight & Market Implications

This detailed bug report exposes a critical divergence in `cn`'s class merging logic compared to `tailwind-merge` and Tailwind v4, specifically concerning arbitrary `font-[...]` values. `cn` incorrectly classifies non-numeric `font-[...]` as `font-weight` instead of `font-family`, leading to incorrect CSS output and unexpected style conflicts. This directly undermines `cn`'s "Full parity" claim and its positioning as a drop-in replacement. Such discrepancies, even if subtle, erode developer trust and necessitate manual workarounds, negating the performance benefits. Achieving true parity in edge cases like arbitrary value parsing is paramount for `cn` to establish itself as a reliable, high-performance alternative in the Tailwind ecosystem.

Proprietary Technical Taxonomy

Raw Developer Origin & Technical Request

GitHub Issue Sep 3, 2026

Repo: shadcn-ui/cn

font-[] is merged as font-weight instead of font-family (differs from tailwind-merge and Tailwind v4)

`cn` classifies a bare arbitrary `font-[…]` value as font-weight regardless of content, while tailwind-merge (and Tailwind v4 itself) treats a non-numeric value as font-family. Found while running a differential of `cn` against `twMerge(clsx(...))` over a real codebase (28M comparisons; this and `@container*` were the only diverging groups).

**Versions:** cn 0.2.4, tailwind-merge 3.4.0, Node 22.

**Repro** (default config, `import { cn } from "cn"` vs `import { twMerge } from "tailwind-merge"`):

| input | tailwind-merge | cn |
|---|---|---|
| `font-sans font-[Inter]` | `font-[Inter]` | `font-sans font-[Inter]` |
| `font-[Inter] font-sans` | `font-sans` | `font-[Inter] font-sans` |
| `font-medium font-[Inter]` | `font-medium font-[Inter]` | `font-[Inter]` |
| `font-[Inter,sans-serif] font-bold` | `font-[Inter,sans-serif] font-bold` | `font-bold` |

Tailwind v4 compiles `font-[Inter]` to `font-family: Inter`, so the third and fourth rows drop a font-weight that should survive, and the first two keep a font-family that should be overridden. tailwind-merge's rule is: `font-[…]` is font-weight only when the value is an arbitrary number (or labelled `weight:`), otherwise font-family.

Related, opposite direction, and arguably a tailwind-merge bug rather than yours: for the labelled CSS-variable shorthand `font-(family-name:--f)`, `cn` correctly puts it in font-family while tailwind-merge's font-weight group swallows it first via its unlabelled `isArbitraryVariable` matcher:

| in...

View Raw Source

Developer Debate & Comments

No active discussions extracted for this entry yet.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from shadcn-ui/cn.

Vite/Next plugins for dev file watcher

Extracted Positioning

Integration of `cn` with development build tools (Vite/Next.js) for file watching.

Achieving full compatibility and optimal performance within modern JavaScript build ecosystems, specifically addressing the "gap" in dev file watching.

Frequently Asked Questions

Market intelligence mapped to `cn`'s class merging logic for arbitrary `font-[...]` values, specifically its differentiation between `font-weight` and `font-family`..

What problem does `cn`'s class merging logic for arbitrary `font-[...]` values, specifically its differentiation between `font-weight` and `font-family`. solve?

Based on our AI analysis of the original developer request, its primary technical positioning is: Achieving "Full parity" with `tailwind-merge` and correct interpretation of Tailwind v4's CSS class semantics, particularly for arbitrary values.

What are the foundational technologies related to `cn`'s class merging logic for arbitrary `font-[...]` values, specifically its differentiation between `font-weight` and `font-family`.?

Our proprietary extraction maps `cn`'s class merging logic for arbitrary `font-[...]` values, specifically its differentiation between `font-weight` and `font-family`. to adjacent architectural concepts including Tailwind class merging, conflict resolution, tailwind-merge, clsx.

Engagement Signals

Replies

open

Issue Status

Cross-Market Term Frequency

Quantifies the cross-market adoption of foundational terms like Tailwind v4 and Tailwind class merging by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.