Varo

Registry-first mobile UI for two runtimes

Varo delivers editable component source, business Blocks, and Agent UI to H5 and Wevu mini-program projects through its Registry while preserving native rendering on each target.

Maintained by: daguanren21 and contributors

Read the docs View source View on npm

Install

ForVue 3 teams that need shared interaction semantics, component source, and business blocks across H5 and mini-program products.

pnpm dlx @varo-ui/cli add --target weapp button input card

Real runtime output

These images come from official project demos or regression baselines and are stored locally on this site.

Varo Agent UI conversation and tool interface — Agent UI and the Agent Chat Block provide conversation, tool-call, and approval interactions.

ENGINEERING PROOF

Registry install command

Start with a real config, command, or boundary note when deciding if this project fits your codebase.

terminalStable

pnpm dlx @varo-ui/cli add \
  --target weapp \
  button input card

Core capabilities

56 H5 Registry component families
45 mini-program Registry component families
Registry and Agent UI
Native Vue 3 and Wevu rendering

Common use cases

01Install editable H5 or mini-program component source from the Registry
02Reuse dual-target business Blocks and Agent UI
03Build a design system on headless primitives and theme tokens

Platforms

H5WeChatVue 3weapp-viteTailwind CSS

weapp-tailwindcss weapp-sqlite

Current version: v2.1.0; Sep 13, 2026
Weekly downloads: 195
GitHub Stars: 2

Frequently asked questions

How is Varo different from a traditional npm UI library?

Varo uses its Registry to install component and Block source into the product repository by default, so teams can modify and own that source.

Which runtimes does Varo support?

H5 uses Vue 3, while mini-program projects use Wevu and weapp-vite. The targets share types, pure functions, and headless primitives.

Future documentation path

`/docs/varo/`

This path will become canonical when aggregated documentation launches.