taro
开放式跨端跨框架解决方案,支持使用 React/Vue 等框架来开发微信/京东/百度/支付宝/字节跳动/ QQ 小程序/H5/React Native 等应用。
Taro: one codebase for mini programs, H5, and React Native
An open, cross platform, cross framework solution that lets teams write one set of code and ship to WeChat, JD, Baidu, Alipay, ByteDance, and QQ mini programs, plus H5 and React Native.
The problem it solves
The README starts from the mess of the front end world. Web, React Native, and the various mini program platforms each demand their own code, and when a product must exist on several of them, writing separate implementations is expensive. Taro's answer is one set of code that adapts to multiple ends. It supports React, Vue, and Nerv as the authoring frameworks. The primary language listed is TypeScript, and the documentation lives at docs.taro.zone.
The target platforms
The platform list is long: WeChat, JD, Baidu, Alipay, ByteDance, and QQ mini programs, plus H5 and React Native apps. The project is developed by the NervJS team. The README's table of contents runs through introduction, learning resources, community sharing, project status, usage cases, joining the build, issue feedback, special thanks, contributors, development plan, changelog, and developer communication, which gives newcomers a clear map of the project.
UI libraries
Several component libraries sit on top of Taro. Taro UI is a multi end UI component library based on Taro for React. NutUI is a JD style, lightweight mobile Vue component library. Taroify is a lightweight mini program Taro component library, and another entry is a UI library based on Vant Weapp that supports Taro and React. They differ by framework and by Taro version, which gives teams a choice depending on their stack.
Docs and project map
Documentation lives at docs.taro.zone. The README structure doubles as a project map: introduction, learning resources, community sharing, project status, usage cases, joining the build, issue feedback, special thanks, contributors, development plan, changelog, and developer communication are all listed as sections. It is a long table of contents for a project that touches many platforms.
The license
The README includes an MIT style license text granting free use of the software, and the project presents itself as open source and community driven. The development plan and changelog are folded into the README structure, along with a special thanks section.
Community notes