Skip to content

Cross-runtime Showcase ​

This is Varo’s public cross-runtime showcase: choose an adoption path first, then distinguish live browser interaction, a browser-rendered Weapp contract preview, and compiled evidence from WeChat DevTools. Repository playgrounds remain maintainer QA surfaces, not the public installation path.

Choose an Adoption Path ​

H5 REGISTRY

H5 Product

pnpm dlx @varo-ui/cli add --target h5 components/button

Installs editable Vue component source and dependencies into the product repository.

WEAPP REGISTRY

Weapp Product

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

Installs target-specific, WXML-safe Wevu SFC source and dependencies into the product repository.

RUNTIME PACKAGE

Centralized H5 Runtime

pnpm add @varo-ui/h5

Consumes the published package when coordinated upgrades are intentional.

Registry installation is the default path. Start with the installation guide, then generate source for the selected target.

H5 Live & Weapp Contract Preview ​

The components below are directly operable. H5 runs real @varo-ui/h5 browser components; switching target is explicitly labelled Weapp Contract Preview so the browser-rendered API and visual contract is not mistaken for the mini-program runtime.

Cross-platform Overview Example and Preview

Invalid state
H5 LiveInteractive browser runtime
Current value: Avery Lin
Dialog PreviewComposable dialog

Weapp DevTools Verified: Compiled Blocks ​

The images below were captured through WeChat DevTools automation from Block pages built by weapp-vite. The evidence snapshot is dated 2026-08-28; inspect the capture script and a representative original image. Every card also links directly to its original image.

Selecting H5 changes the install command and usage code only. When the repository has no published H5 image for that Block, the card continues to identify the image as Weapp DevTools Verified instead of implying that the H5 selector changed it.

Evidence and Implementation Boundaries ​

  • H5 Live: real browser components and interactions on this page
  • Weapp Contract Preview: a browser-rendered target contract, not the WeChat runtime
  • Weapp DevTools Verified: DevTools evidence from a compiled mini-program page
  • weapp-vite owns component JSON, complex list keys, generated types, and target output; wevu is the runtime peer for @varo-ui/weapp
  • weapp-tailwindcss translates classes in the build chain; native hover-class provides mini-program pressed feedback

Continue ​