Planned

Varo

Production foundation for cross-runtime component systems

Registry-first primitives, UI wrappers, theme tokens, business blocks, and Agent UI for H5 and weapp-vite mini-programs, delivered as editable source through the CLI.

Read the docs View source View on npm

Varo documentation home showing the cross-runtime component system — Varo unifies H5 and mini-program component systems through primitives, editable source, and delivery checks.

Install

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

pnpm dlx @varo/cli add --target weapp-vite 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 — Thirty-six dual-target Agent UI components and the Agent Chat Block share one event protocol.

Core capabilities

56 dual-target runtime families
45 mini-program registry families
36 dual-target Agent UI components
Registry-first source delivery

Common use cases

01Install editable H5 or mini-program component source from the registry
02Reuse dual-target business blocks and Agent UI
03Build an internal design system from primitives and theme tokens

Platforms

H5WeChatVue 3weapp-viteTailwind CSS

Current versionv0.0.1Aug 26, 2026

Weekly downloads0

GitHub Stars0

Frequently asked questions

How is Varo different from a traditional npm UI library?

Varo primarily delivers component and block source that teams can copy, modify, and own instead of a black-box UI package that is customized only from the outside.

Which runtimes does Varo support today?

The registry targets H5 and weapp-vite. Both runtimes maintain 56 component families, while the mini-program registry currently exposes 45 high-consensus families.

Future documentation path

`/docs/varo/`

This path will become canonical when aggregated documentation launches.