Button Variants
The cva variant map that `button.tsx` imports — variant × size class strings and nothing else. Pure CVA: no React, no client APIs, so a server component can style a plain `<a>` with `buttonVariants({ variant, size })`.
Preview
Rendered from the story the storybook (a11y) CI gate runs axe against — the preview can't show something that hasn't been verified.
Install
Two equivalent paths — the URL works in any shadcn-CLI setup; the alias works once you've registered @interlace in your components.json.
npx shadcn@latest add https://ds.interlace.tools/r/button-variants.jsonnpx shadcn@latest add @interlace/button-variantsBehavior
What this component does — the keyboard path, the measured colour, the text equivalent and the states it can be in. Every figure below is read out of the test or the source that enforces it by scripts/build-behavior-map.mjs, so nothing here can outlive the gate that keeps it true.
Measured contrast
packages/ui/__tests__/theme-contract-lock.test.ts ↗Every semantic colour pair this component's own source uses, measured against the shipped hexes in all 4 theme × scheme combinations. The tightest is input on card at 3.11:1 (interlace · dark), against a floor of 3:1.
| Pair | interlacelight | interlacedark | harborlight | harbordark | Floor |
|---|---|---|---|---|---|
| input on cardcontrol border inside a card | 3.62:1 | 3.11:1 | 3.62:1 | 3.85:1 | 3.0:1SC 1.4.11 |
| input on backgroundcontrol border (SC 1.4.11) | 3.62:1 | 3.35:1 | 3.43:1 | 4.25:1 | 3.0:1SC 1.4.11 |
| destructive on backgrounddestructive tint on the page surface | 8.31:1 | 10.43:1 | 7.60:1 | 10.03:1 | 3.0:1SC 1.4.11 |
| destructive-foreground on destructivecopy on a destructive face | 8.31:1 | 10.43:1 | 8.02:1 | 10.03:1 | 4.5:1SC 1.4.3 |
| destructive on carddestructive tint inside a card | 8.31:1 | 9.66:1 | 8.02:1 | 9.09:1 | 3.0:1SC 1.4.11 |
| ring on backgroundfocus ring (SC 2.4.13) | 8.80:1 | 11.79:1 | 8.39:1 | 10.03:1 | 3.0:1SC 1.4.11 |
| primary on backgroundprimary tint on the page surface | 8.80:1 | 11.79:1 | 8.39:1 | 10.03:1 | 3.0:1SC 1.4.11 |
| ring on cardfocus ring inside a card | 8.80:1 | 10.92:1 | 8.86:1 | 9.10:1 | 3.0:1SC 1.4.11 |
| primary-foreground on primarycopy on a primary face | 8.80:1 | 11.79:1 | 8.86:1 | 10.03:1 | 4.5:1SC 1.4.3 |
| primary on cardprimary tint inside a card | 8.80:1 | 10.92:1 | 8.86:1 | 9.10:1 | 3.0:1SC 1.4.11 |
| accent-foreground on accenthover/highlight face | 8.98:1 | 10.46:1 | 8.95:1 | 9.65:1 | 4.5:1SC 1.4.3 |
| secondary-foreground on secondarysecondary button face | 15.58:1 | 14.51:1 | 14.63:1 | 14.04:1 | 4.5:1SC 1.4.3 |
| foreground on backgroundbody copy | 19.65:1 | 16.97:1 | 17.74:1 | 16.19:1 | 4.5:1SC 1.4.3 |
Text pairs are held to 4.5:1 (WCAG 2.2 SC 1.4.3); borders, rings and chart axes to 3:1 (SC 1.4.11 non-text). Bold is the worst cell in the row — the one a brand fork has to keep an eye on.
Runtime contract
packages/ui/vitest.config.ts ↗Where it renders, how narrow it survives, and whether its lines are inside the coverage gate — three answers a consumer needs before the paste, not after the bug.
- Render boundary
server componentRenders during SSR / RSC with no hydration cost. It can be imported from a server component without pulling the page into the client.
- Minimum viewport
none declaredNo width floor: it takes the width it is given. Its container owns the layout question.
- Coverage gate
100% × 4Inside the v8 gate: lines 100, statements 100, functions 100, branches 100. A threshold under 100 only records how much you stopped caring, so there isn't one.
History
This component is at v1.3.0, first shipped in @interlace/ui 1.0.0. The version is stamped as a banner into the file the install writes, so the copy in your tree says which one you have — compare it with the number above before deciding whether to re-run the install.
No release note names this component yet. It shipped with the release above and has not changed since — see the full changelog for what moved elsewhere in the DS.
Import
Single named export.
import { buttonVariants } from '@/components/ui/button-variants';Anatomy
Extracted from the primitive's JSDoc header. The source is the only documentation that can't drift.
buttonVariants({ variant, size })
├─ variant default | destructive | outline | secondary | ghost | link
└─ size default | xs | sm | lg | icon | icon-xs | icon-sm | icon-lg
Defaults are `variant: 'default'`, `size: 'default'`. `pagination.tsx` is
the in-repo example of styling an element rather than nesting a Button: its
`<a>` takes `buttonVariants({ variant, size })` directly. (It reaches the
function through `button.js`, which re-exports it — that path is
`'use client'`; import from this module to keep a server tree server-side.)Variants
Closed prop unions enforced by class-variance-authority. See Storybook's Variants story for the rendered matrix.
- variant
- defaultdefault
- destructive
- outline
- secondary
- ghost
- link
- size
- defaultdefault
- xs
- sm
- lg
- icon
- icon-xs
- icon-sm
- icon-lg
Accessibility
Every story for this component is rendered headlessly and checked with axe-core (wcag2aa, wcag22aa, best-practice, ACT) on every PR. That gate has no continue-on-error, so what ships has zero known violations.
What follows is what static analysis can see. Axe cannot press a key and never sees an overlay open, so the operable-without-a-mouse claim lives in Behavior instead, where the keyboard path is replayed step by step.
- Focus + keyboard behaviour
- Native element semantics — no interaction layer to get wrong.
- Focus ring (WCAG 2.2 SC 2.4.13)
- Inherited from the preflight focus contract shipped in @interlace/theme.
- Reduced motion
- No animation to gate.
- ARIA in the source
aria-invalid
R-rule compliance
Every primitive in @interlace/ui models to the portable 26-rule floor enforced by the componentApi ESLint preset. The cells below pin exactly where each rule applies in this file.
| Rule | Concept | Where |
|---|---|---|
| R8 | Enums, no booleans | `variant` and `size` are closed string enums |
| R19 | Tokens only | `bg-primary`, `bg-destructive`, `bg-accent`, `ring-ring/50` |
| R20 | AA contrast | every pair composited by `composite-contrast-lock` |
| R25 | Server-safe | no React import, no hooks, no `'use client'` |
Dependencies
- Base UI primitive
- Native / no Base UI dependency
- Lucide icons
- none
- NPM dependencies
class-variance-authority
- Registry dependencies
Source
The full implementation — components/ui/button-variants.ts once installed.
import { cva, type VariantProps } from 'class-variance-authority';
// @interlace/button-variants v1.3.0 — Interlace design system.
// Docs, props and live preview: https://ds.interlace.tools/c/button-variants
// What changed since: https://ds.interlace.tools/c/button-variants#history
// Generated banner — keep it, the upgrade diff reads this version.
/**
* @interlace/ui — buttonVariants
*
* The cva variant map that `button.tsx` imports — variant × size class strings
* and nothing else. Pure CVA: no React, no client APIs, so a server component
* can style a plain `<a>` with `buttonVariants({ variant, size })`.
*
* This is not a component. It exports a function and a type, renders nothing,
* and has no props, no slots and no DOM — which is exactly why it is a
* separate module from the `'use client'` Button that consumes it.
*
* ## Anatomy
*
…123 more lines…Registry JSON
The raw registry record — what the shadcn CLI fetches.