FAQ

Quick answers to the questions that come up most. Still stuck? Check the contributing page for the repo.

Is Lerpa UI free?

Yes — completely free and open source under the MIT license. Use it in personal and commercial projects without attribution requirements or a paid tier.

Is it React-only?

Yes. Components are written in React 19 with TypeScript. They're plain .tsx files, so they work in any React framework — Next.js 16, Vite, Remix, and so on — but there's no Vue, Svelte, or web-component build.

Do I need Tailwind v4?

Yes. Components are styled with Tailwind CSS v4and a CSS-variable token system. You'll want Tailwind v4 configured in your project; the init command helps wire it up.

How do updates work?

Because components are copy-paste, there's no version to bump in package.json. To get the latest version of a component, re-add it (lerpa-cli add <id>) or run lerpa-cli update. Since you own the file, review the diff before committing if you've customized it.

How is it different from shadcn/ui?

Lerpa UI shares shadcn's philosophy — copy-paste source you own, distributed through a registry — and the registry is shadcn-compatible, so you can even install components with npx shadcn add https://lerpaui.com/r/<id>.json. The differences are scope and style: a much larger catalog (1000+ components, 24 animated charts, ~180 page blocks), motion baked in with Framer Motion, a distinct mono-accent aesthetic, and first-class AI tooling via the MCP server and llms.txt.

Can AI agents install components?

Yes. The MCP server exposes the catalog to assistants like Cursor and Claude Code so they can search and install components for you, and llms.txt makes the catalog legible to AI crawlers.

Is it accessible?

Yes — components target WCAG 2.1 AA, are axe-tested, keyboard-navigable, and respect prefers-reduced-motion. See the accessibility guide.