Library / SDK
unovue/reka-ui avatar
unovue/reka-ui

Reka UI: a Vue component library with a pnpm workspace behind it

An open-source UI component library for building high-quality, accessible design systems and web apps for Vue. Previously Radix Vue

6,958 stars585 forksVueMIT

At a glance

What is it?
Reka UI is the Vue component library formerly called Radix Vue, MIT licensed and published from packages/core. Its root README.md points to ./packages/core/README.md, so the release path, the git hooks and the gaps in the documentation are where the real information sits.
Who is it for?
Reka UI suits a Vue team that wants a component library where accessibility is the stated goal, and it is unsuitable if you need a React port or a themed set of finished components. Before adopting, pick the install line for the package manager you already use, pin a version on the 2.11 line rather than tracking the default branch, and remember that publishing runs from packages/core while the version string is bumped in three manifests at once.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Vue, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • unovue/reka-ui6,958 ★ · +130
Star history
Repository2026-09-232026-11-15
unovue/reka-ui6.8k7k

130 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The package was Radix Vue before the rename

The repository description carries the rename in plain text: an open source UI component library for building accessible design systems and web apps for Vue, previously Radix Vue. The two names are therefore the same project rather than a fork. The default branch is named v2 rather than main, so a fresh clone lands on the 2.x line with no branch switching. Any comparison that starts from the name alone will get this wrong.

Three one-line installs and no setup step

Installation is one command per package manager.

bash
pnpm add reka-ui
bash
npm install reka-ui
bash
yarn add reka-ui

One package name, reka-ui, works for all three managers, and the project documentation is at reka-ui.com.

The docs site needs a build before pnpm docs:dev

Running the documentation locally takes four steps: clone the repo, run pnpm i, run pnpm build to build reka-ui locally, then run pnpm docs:dev. The build step comes before the dev server, which is easy to miss because docs:dev is filtered to the docs workspace and expects library output to already exist. A second track covers component work: clone, run pnpm i, then pnpm story:dev opens histoire, and pnpm test runs the suite. Both tracks share pnpm i and nothing else, so alternating between documentation and components means keeping two long-running processes alive.

package.json is private while the workspace publishes

The root manifest carries "private": true, "workspaces": ["packages/*"], and "packageManager": "[email protected]", with a pnpm-workspace.yaml file beside it. Version 2.11.0 also appears in that root manifest, which is the part worth pausing on. bumpp is invoked against package.json, packages/*/package.json and docs/package.json in one command, so three manifests have to agree on a release number, and nothing in the README explains why the number is duplicated rather than derived at publish time. For a consumer installing by package name this changes nothing. For anyone reading the repository to work out what is about to ship, it is one more file to check before a release goes out.

The release script runs from packages/core

Publishing is not wired at the workspace root. The pub:release script reads:

bash
cd packages/core && pnpm pub:release

The published artifact is therefore produced from one package directory, and the root build script has the same shape, filtering twice: pnpm run --filter reka-ui build && pnpm run --filter plugins build. The plugins target has no matching entry in the top-level listing, which shows packages/ as a directory without its contents, so what else gets built has to be read out of that directory directly. Put together with the three-manifest version bump, the release path has three moving parts, and none of them are described in the README.

Lint runs against every staged file through git hooks

Quality control is set up with git hooks rather than CI instructions. simple-git-hooks installs on prepare and wires two steps: a pre-commit hook running pnpm lint-staged, and a commit-msg hook running pnpm commitlint --edit, with commitlint extending @commitlint/config-conventional. lint-staged then applies eslint --fix to every staged file through a "*" pattern. At the root, lint is eslint. and lint:fix is eslint. --fix, driven by eslint.config.mjs and @antfu/eslint-config. TypeScript is pinned at 5.8.3 in devDependencies, and the test scripts are filtered to the package, so pnpm test maps to pnpm --filter reka-ui test with test:run and test-update beside it. Contributors need those hooks installed, which is why prepare runs simple-git-hooks during install.

What the repository leaves open

Several things an evaluator will want are simply absent. The accessibility claim in the repository description is a goal rather than a tested result. The top-level listing also carries CLAUDE.md, .coderabbit.yaml, patches/, playground/ and typos.toml, none of which the README explains. Anyone deciding on this library has to read the tree, not just the readme.

Editorial conclusion

Reka UI suits a Vue team that wants a component library where accessibility is the stated goal, and it is unsuitable if you need a React port or a themed set of finished components. Before adopting, pick the install line for the package manager you already use, pin a version on the 2.11 line rather than tracking the default branch, and remember that publishing runs from packages/core while the version string is bumped in three manifests at once.

Frequently asked questions

What is Reka UI and what was it called before?

It is an open source UI component library for building accessible design systems and web apps for Vue, MIT licensed. The repository description records the earlier name, Radix Vue.

How does Reka UI relate to Radix Vue?

Reka UI was previously Radix Vue, so the two names refer to the same project.

How do I install Reka UI?

Pick the line for your package manager: pnpm add reka-ui, npm install reka-ui, or yarn add reka-ui.

How do I run the Reka UI documentation locally?

Clone the repo, run pnpm i, then pnpm build, then pnpm docs:dev. For component work, pnpm story:dev opens histoire and pnpm test runs the suite.

Where does a Reka UI release get published from?

The pub:release script changes into the package directory first: cd packages/core && pnpm pub:release. The version number is bumped separately in package.json, packages/*/package.json and docs/package.json by bumpp.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. unovue/reka-ui on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/unovue-reka-ui.svg)](https://hysenlabs.com/projects/unovue-reka-ui)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/unovue-reka-ui.svg)](https://hysenlabs.com/projects/unovue-reka-ui)

Was this useful?