# Radix or Base UI

Wisty UI ships every component for two component libraries, Radix and Base UI, as shadcn does. The components look the same on either, and each keeps the API shadcn gives it on that library, so code written against shadcn's component works unchanged. A few interactions follow the library, like whether tabs select on focus.

## Which one you get

The one your project already uses. The CLI reads the style in your `components.json` and installs the matching file, so you never choose per component.

- New shadcn projects start on Base UI. `shadcn init -b radix` starts one on Radix.
- Salesforce's React template is on Radix.
- React Aria, shadcn's third component library, isn't supported.

## What differs

A test renders every example on both libraries and fails if their styles differ anywhere it doesn't expect. The code differs where shadcn's does:

- Composition: Radix components take `asChild`, Base UI components take `render`.
- A few props, like toggle group's `type="single"` on Radix and `multiple` on Base UI.
- The package each file imports: `radix-ui` or `@base-ui/react`. Combobox and Date picker import `@base-ui/react` on Radix too, as shadcn's Radix Combobox does, so a Radix project that installs them, or an item built on them like Lookup, has both packages. They work side by side.

## On this site

On a component's page, pick your project's library under Library, beside On this page, or under the title on a narrow screen. Code samples, manual installs and the API reference then match it, and the site remembers your choice.