StableVaro
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.
Install
Vue 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 cardReal runtime output
These images come from official project demos or regression baselines and are stored locally on this site.
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
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 are h5 and weapp, with mini-program components integrating with 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.