English | 简体中文
Documentation · GitHub Release · npm organization
Varo is a registry-first component system for Vue 3 mobile H5 applications and weapp-vite mini programs. Its primary product is editable, target-specific component and Block source code that becomes part of the consuming application—not an opaque cross-platform UI runtime.
@varo-ui/cli— installs editable Registry source for H5 and Weapp targets@varo-ui/headless— runtime-neutral state machines, events, controlled-state contracts, and utilities@varo-ui/h5— tree-shakeable Vue components for mobile H5 products@varo-ui/weapp— component wrappers for theweapp-vitebuild chain@varo-ui/theme— shared theme tokens and providers@varo-ui/ai— Agent event protocol, streaming controller, SSE/chunk decoding, and safe Markdown model
- H5 runtime catalog: 56 component families
- Weapp runtime catalog: 56 component families; copy-owned Registry renderers ship as target-specific native Wevu SFCs, while pure adapters may re-export target primitives across the 45 high-consensus families plus
RegionPickerand nativeMap - Agent Core: shared event protocol, SSE/chunk transport, Markstream scheduling on H5, timed-frame scheduling on mini programs, and a safe incremental Markdown AST
- Agent UI: 42 dual-target components plus Agent Chat and Agent Workspace Blocks for scoped context, visible retrieval, tasks, thread versions, placement shells, conversations, streaming, tools, approvals, code, diffs, citations, media, tables, and workflows
- Dual-target Blocks: Login Form, Profile Card, Profile Edit, Product List, Order Filter, Agent Chat, and Agent Workspace
- AI commerce demo: real incremental events, reasoning and tool states, human approval for purchases and returns, order history, and address configuration
- Registry targets:
h5andweapp - Mini-program styling: Tailwind CSS v4,
weapp-tailwindcss, and@weapp-tailwindcss/merge - Mini-program debugging: built-in MCP, DevTools console bridge, Automator screenshots, and runtime smoke checks
- The high-consensus Weapp Registry is based on the overlapping capabilities of Vant Weapp, NutUI, TDesign Mobile Vue, and TDesign MiniProgram.
- Motion and Agent interaction patterns reference Beautiful UI and beUI, while production code remains native to Vue and mini-program runtimes.
- Both runtime catalogs contain 56 component families. The Weapp Registry exposes 45 high-consensus families plus
RegionPickerand nativeMap;calendar,cascader,date-picker,elevator,fixed-nav,number-keyboard,picker,range,short-password,side-navbar, anduploaderremain runtime-only until their native WeChat interactions are verified. - H5 streaming uses Markstream Core scheduling and Markdown parsing. Mini programs use the same protocol and AST with a timed scheduler that does not depend on
requestAnimationFrame. - The machine-readable boundary is defined in
registry/component-tiers.v0.1.json.
# Native mini-program SFCs
pnpm dlx @varo-ui/cli add --target weapp button input card
# H5 source
pnpm dlx @varo-ui/cli add --target h5 button input card
# Dual-target business Block
pnpm dlx @varo-ui/cli add --target weapp blocks/product-list
# Dual-target Agent Chat Block
pnpm dlx @varo-ui/cli add --target weapp blocks/agent-chat
pnpm dlx @varo-ui/cli add --target h5 blocks/agent-chat
# Agent UI suite
pnpm dlx @varo-ui/cli add --target weapp components/agent-ui
pnpm dlx @varo-ui/cli add --target h5 components/agent-ui
# High-consensus mini-program components
pnpm dlx @varo-ui/cli add --target weapp action-sheet collapse dialog list notice-bar popover skeleton stepsThe CLI does not overwrite existing files by default. Use --force only after confirming that local customizations may be replaced.
pnpm dev:playground-h5
pnpm --filter @varo/playground-weapp dev:aidev:ai prepares the WeChat DevTools project, starts the MCP HTTP service, and forwards DevTools console output and uncaught errors to the active terminal.
pnpm run docs:devThis starts VitePress at http://localhost:5173 with in-page H5 and Weapp component previews.
pnpm typecheck
pnpm test
pnpm buildSee RELEASING.md for the repoctl, npm OIDC, and documentation deployment workflow.