VPT
Vite for Taro projects
Use Vite for Taro development and builds instead of the older webpack pipeline. It connects existing React projects to the toolchain.
Maintained by: sep2 and contributors
Adjacent tools and runtime capabilities can be composed as needed without migrating an entire project at once.

Install
ForFrontend teams that want to reuse React and Taro components and APIs while developing WeChat, Alipay, and Web apps with a modern Vite toolchain.
npm install -D vite-plugin-taroReal runtime output
These images come from official project demos or regression baselines and are stored locally on this site.


ENGINEERING PROOF
Taro + Vite migration
Start with a real config, command, or boundary note when deciding if this project fits your codebase.
npm create vite-taro@latest my-app
# keep React + Taro APIs
# move the build pipeline to ViteCore capabilities
- Vite 8 + React 19 + Taro 4
- State-preserving hot reload
- Automatic WeChat subpackages
- Tailwind CSS v4 out of the box
- WeChat Skyline rendering
Common use cases
- 01Create a cross-platform React project with npm create vite-taro@latest my-app
- 02Edit React components in WeChat DevTools while preserving page, component, and input state
- 03Plan WeChat mini-program subpackages automatically from standard static and dynamic imports
Platforms
Related projects
- Current version
- v0.7.1
- Sep 7, 2026
- Weekly downloads
- 934
- GitHub Stars
- 50
Frequently asked questions
How does VPT relate to Taro?
VPT is short for vite-plugin-taro. It uses Taro components, APIs, and runtime with Vite-powered development and builds instead of the older webpack pipeline.
Which platforms does VPT support?
VPT currently supports WeChat mini-programs, Alipay mini-programs, and the Web (H5), using the wx, zfb, and h5 build targets respectively.
How do I get started with VPT?
For a new project, run npm create vite-taro@latest my-app. For an existing Taro project, follow the official migration guide; installing the plugin still requires configuring Vite and project entries as documented.
Future documentation path
/docs/vite-plugin-taro/
This path will become canonical when aggregated documentation launches.