class-variance-authority

A tiny TypeScript utility for building type-safe, variant-driven className APIs on top of clsx.

Library
npm
v0.7.1
6,903 stars
Apache License 2.0

Repository Health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum. How we score it →
82 /100 Excellent
Development Activity 96
Maintenance 84
Community 52
Maturity 56
Momentum 40

Technical Analysis

AI-assessed by reading the actual repository — architecture, code quality, innovation, and documentation. How we score it →
87 /100 Excellent
Architecture 85
Code Quality 82
Innovation 88
Learning Curve 92

class-variance-authority (CVA) lets you define a component’s visual variants — size, intent, state, and any compound combination of them — as a single declarative config object, then resolves the right class string at call time based on the props passed in. It wraps clsx internally so you still get array/object/conditional class syntax for free, but adds a typed layer on top: TypeScript infers your component’s prop types directly from the variant config via the exported VariantProps helper, so variant names and their allowed values stay in sync between the styling definition and the component’s public API. Originally built for Stitches-style variant ergonomics without a CSS-in-JS runtime, CVA has become the de facto variant-composition primitive behind shadcn/ui and a large share of the Tailwind CSS component ecosystem.

What You Get

  • The cva() factory — declare base classes, variants, defaultVariants, and compoundVariants once, get back a function that resolves to a class string per call
  • cx — a direct re-export of clsx for plain conditional class concatenation outside of a variant config
  • VariantProps<T> — a TypeScript helper that derives a component’s prop types straight from its cva() config, so variant names/values can’t drift out of sync with the component signature
  • A class/className escape hatch on every generated function, so callers can always merge in ad-hoc classes on top of the resolved variant output
  • Zero CSS-in-JS runtime — output is a plain string, so it works with Tailwind, CSS Modules, vanilla-extract, or hand-written CSS equally well

Common Use Cases

  • Defining variant props (size, variant, disabled) for a shadcn/ui-style Button, Badge, or Alert component built on Tailwind CSS
  • Sharing one variant config between multiple sibling components (e.g. Button and IconButton) that need consistent size/intent options
  • Replacing hand-rolled clsx(…) ternary chains in design-system components with a single declarative config that’s easier to review and extend
  • Building framework-agnostic style logic (React, Vue, Svelte, Astro) since cva() returns a plain string and has no framework-specific dependency

Under The Hood

Architecture The core implementation lives entirely in packages/class-variance-authority/src/index.ts (~150 lines), exporting two primitives: cx (a direct re-export of clsx for raw class concatenation) and cva (a curried factory function). Calling cva(base, config) returns a props-accepting function; internally it walks config.variants via Object.keys, resolves each variant’s selected key against props or config.defaultVariants using a falsyToString helper (so false/0 variant keys aren’t coerced away), then reduces config.compoundVariants against the merged props+defaults to append additional classes, finally concatenating everything through clsx (cx) alongside any props.class/props.className escape hatch. There is no internal state, no classes, no external I/O — it’s a pure, synchronous class-string composition pipeline. Types (VariantProps, ConfigSchema, etc.) are isolated in src/types.ts and lean on TypeScript generics/conditional types to give callers compile-time-checked variant props. The repo is a pnpm workspace housing this package plus a parallel v1 rewrite (packages/cva, still in beta) and a docs Astro site (docs/), but the shipped runtime surface of class-variance-authority itself is intentionally minimal.

Tech Stack TypeScript-only source (99.75% per GitHub language stats). Single runtime dependency: clsx (^2.1.1). The build tool is tsdown (a Rolldown-based bundler) producing dual ESM/CJS output plus .d.ts types. Dev tooling includes @arethetypeswrong/core and publint for package-export correctness checks, size-limit enforcing a 1.2KB budget on dist/index.js, TypeScript 6.0.3 for type-checking, and react/react-dom as devDependencies only (used to type-test VariantProps against component prop shapes, not as a runtime dependency). Package manager is pnpm with a workspace tying the core package to the docs site and the parallel v1 rewrite.

Code Quality packages/class-variance-authority/src/index.test.ts is a single but substantial 1766-line test file exercising variant resolution, defaultVariants, compoundVariants (including array-valued compound matching), null-variant overrides, and TypeScript type inference via type-only assertions. The implementation favors small, named helper functions (falsyToString) and explicit reduce/map compositions over cleverness; there are no custom error classes or thrown exceptions because the API can’t fail at runtime — invalid variant keys are caught at the type level rather than checked at runtime, a deliberate zero-runtime-validation design suited to a hot-path styling utility.

API Design The public API is two functions (cx, cva) plus one exported type helper (VariantProps<T>), which keeps the learning curve nearly flat: define variants as a nested object literal, call the returned function with a subset of variant keys, get a class string back. VariantProps<typeof myCva> lets consumers derive component prop types directly from the variant config instead of duplicating them — the library’s signature ergonomic win, and exactly what shadcn/ui-style component libraries lean on. The class/className escape hatch is a small but consistent affordance for merging caller-supplied classes on every call site. Documentation lives off-repo at cva.style (an Astro site checked into docs/) rather than in the README, keeping the README itself terse — good for npm page browsing, though GitHub-only visitors get less immediate context than the docs site provides.

Used by 191 apps in this directory

Python
78%
AGPL 3.0

Skyvern

AI Agents · Automation

23,168

Skyvern (YC S2023) automates browser-based workflows by pairing LLMs with computer vision, letting agents click, fill, and extract data on sites they've never seen, without brittle XPath selectors that break on every layout change.

View details
89
Repo Health
82
Technical
70
Dependency
Built with
Python 78%
TypeScript 20%
Updated today
TypeScript
97%
AGPL 3.0

Snapify

Collaboration · Productivity

1,018

Open-source, self-hostable screen recording and video sharing built as a Loom alternative — no accounts required to watch, full S3-backed storage for your data.

View details
38
Repo Health
68
Technical
69
Dependency
Built with
TypeScript 97%
Updated 1 years ago
PHP
47%
AGPL 3.0

solidtime

Invoicing Finance · Productivity

8,984

Modern open-source time tracker for freelancers and agencies with invoicing, multi-org support, and Toggl/Clockify migration built in.

View details
84
Repo Health
81
Technical
70
Dependency
Built with
PHP 47%
TypeScript 29%
Vue 22%
Updated yesterday
TypeScript
97%
Other

Sourcebot

AI Code Assistants · Developer Tools · Search

3,985

A self-hosted, AI-powered code search engine that indexes every repo across GitHub, GitLab, Bitbucket, Gitea, Gerrit, and Azure DevOps, so both engineers and coding agents can search, browse, and ask questions about your codebase from one place.

View details
87
Repo Health
83
Technical
61
Dependency
Built with
TypeScript 97%
Updated today
Rust
79%
AGPL 3.0

Spacedrive

Collaboration · File Storage

39,084

One file manager for all your devices and clouds — powered by a Virtual Distributed File System built in Rust.

View details
86
Repo Health
84
Technical
64
Dependency
Built with
Rust 79%
TypeScript 18%
Updated yesterday
TypeScript
97%
MIT

SplitPro

Invoicing Finance

1,468

Self-hosted, open source expense splitting with multi-currency, recurring bills, and bank imports — a complete Splitwise replacement you control.

View details
85
Repo Health
77
Technical
69
Dependency
Built with
TypeScript 97%
Updated today
Ruby
63%
BSD 3

Spree Commerce

CRM · Ecommerce · Marketing

15,749

Open-source headless eCommerce platform with a REST API, TypeScript SDK, and Next.js storefront for B2B, cross-border, and marketplace commerce — no vendor lock-in, no platform fees.

View details
91
Repo Health
84
Technical
81
Dependency
Built with
Ruby 63%
TypeScript 36%
Updated yesterday
TypeScript
89%
Other

Hexclave

Authentication · Developer Tools

6,859

The open-source user infrastructure platform — authentication, teams, payments, emails, analytics, and more on a single unified user model.

View details
88
Repo Health
80
Technical
66
Dependency
Built with
TypeScript 89%
Updated today
TypeScript
94%
Other

Suna

AI Agents

20,262

Turn your company into a git repo — one config, one command center, a workforce of AI agents that runs the real work around the clock.

View details
90
Repo Health
79
Technical
65
Dependency
Built with
TypeScript 94%
Updated today

Join founders buildingwith open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on Substack
Join 750+ subscribers