Merge class names without conflicts

At a glanceCopy Anchor Link

• Who: Developers composing conditional Tailwind classes.
• What: Merge class lists so conflicting utilities resolve to the last one.
• Use when: Whenever classes are conditional or come from props.
• Avoid when: For static class strings — write them directly instead.

InstallCopy Anchor Link

pnpm add @zedtech/zedkit-ui

Latest: 0.3.0 (via changesets).

ExampleCopy Anchor Link

import { cn } from "@zedtech/zedkit-ui";
cn("px-4", isActive && "bg-accent"); // "px-4 bg-accent"
cn("px-4", "px-2"); // "px-2" — last conflicting utility wins

Wraps: clsx, tailwind-merge