FAQ

Yes, the CLI is. Components are still just files you copy: run npx @agents-npm-packages/vibeui to add them, and nothing is installed into your project.

MIT. You can use, modify and ship it commercially. Keep the license notice with copied files where required. Third-party dependencies keep their own licenses: see THIRD_PARTY_NOTICES.md in the repo.

Same copy-owned philosophy and familiar API conventions, but VibeUI has no headless primitives dependency, builds motion into every component, ships one token file that includes keyframes and the dark variant, and adds signature, text, hover and footer components. See the comparison on the introduction.

There is no library bundle: you ship only the files you add and their four peers. A typical component is 1–6 KB of source.

clsx and tailwind-merge combine class names safely, class-variance-authority declares variants, and @phosphor-icons/react provides icons. Nothing else is required at runtime.

React 18 and newer. Components use useId and useSyncExternalStore. The showcase site runs React 19.

No. The token file uses Tailwind v4 features (@theme, @custom-variant, CSS-first configuration). Components also use v4 utilities such as size-* and individual transform properties.

Yes. Files without "use client" are server-safe. Interactive ones are client components and can be imported from Server Components; just do not pass functions from the server. The components page lists which is which.

Yes. Vite, Remix / React Router, Astro with React islands and others work. Only the path alias and the Tailwind plugin differ. See Installation.

Not if you add the inline theme script. See Dark mode.

Current evergreen browsers. A few effects use newer CSS: color-mix(), individual transform properties, mask-image and the animation-timeline-free CSS only. Older browsers degrade to flatter styling rather than breaking.

It uses native controls and real roles, and states its gaps honestly. See Accessibility. It has not had a formal audit.

Not a unit-test suite yet. The repository is checked with TypeScript, ESLint and a production build. Contributions of tests are welcome.

Commit, re-run add for it, and use your Git diff to port any local edits. Components are small and self-contained, so this is quick.

Delete its file. There is no registry state in your project to clean up.

Yes. Pass --dir to the CLI and adjust imports. Components import each other with relative paths (./button) so they keep working together.

Yes: use the MCP server, the CLI with --json, or point it at llms.txt. See Agents and MCP.

See Contributing. Bug reports with a reproduction are the most useful thing you can send.