Radix UI

Why it's ranked here

The engineering discipline is the reason to trust it. Continuous integration fails if any published package can neither be imported inside a React Server Component nor declare itself a client boundary, and a second static check rejects the two ref-composition patterns that caused infinite render loops under React 19. Accessibility assertions run in both unit and browser tests. Against that, the guiding-principles document leaves its documentation section as an unwritten placeholder, and it promises minimal reset styles that the same document elsewhere says are absent. The machine-checked parts are the credible parts, and they are the ones that matter.

What's good

Unstyled composes with any styling approach, so nothing has to be overridden. The umbrella package re-exports every primitive as a namespace, so you install one dependency or pick packages individually. Stateful components work controlled or uncontrolled. Experimental components carry an explicit unstable prefix, which labels the risky surface instead of hiding it. React and its companion packages are pinned to a single version across the workspace, so the tested combination is the shipped combination. MIT licensed, with versioning automated and release candidates published on every merge to the main branch.

Tradeoffs

No styles means no starting look: every visual decision, including the ones that make a menu feel finished, is yours. It is React only, and the workspace pins a single React 19 release, so older React or another framework is out. Documentation lives in a separate repository, so the tree alone will not teach you the APIs. Two components are marked unstable and can change. Splitting each widget into trigger, portal, content and item exports makes even a simple menu verbose, which is the price of getting a real element for every part.

How to use it well

Reach for this when you are building your own design system and want the interaction and accessibility layer solved rather than a look handed to you. It suits teams already on React 19 who write their own CSS and want each widget part to be a real element they can target. It does not give you a theme, tokens, a spacing scale or finished visuals, and it deliberately skips purely presentational pieces such as containers, chips and badges. If you want something that looks done on install, choose a styled kit instead.

Observed

License

MIT, copyright WorkOS

Language

TypeScript only, with local scripts allowed to be type-checked JavaScript

Interface

React component library imported as JSX, no CLI

Install surface

npm packages, one per primitive plus an umbrella package that re-exports them all

Styling

Ships with no presentational styles, styling tool left entirely to the consumer

Server rendering

Client-only packages declare a client boundary directive so they can be imported from React Server Components

Testing

Unit tests with vitest, end-to-end tests with playwright on chromium, accessibility assertions via axe in both layers

Repo layout

pnpm workspace monorepo, versioned and published with changesets, storybook for component examples