This article explains how to adapt GrowingIO's no‑embed SDK for Taro 3 by intercepting runtime events and using a Babel plugin to preserve user method names, achieving a stable zero‑tracking solution for mini‑programs.
This article explains Taro 3.0's approach to bridging the gap between web and mini‑program ecosystems by mapping HTML tags, attributes, and events to mini‑program components, handling style translation, and detailing limitations and practical steps for integrating WEUI, Ant Design Mobile, and VantUI.
Taro 3.2 introduces a revamped compilation pipeline that eliminates intermediate code, adds native source‑map support, supports React Native 0.64 with Hermes, expands APIs and components, enables on‑demand imports, and provides clear migration steps for both new and existing projects, while outlining future roadmap and community resources.
This article walks through the three animation approaches supported by WeChat mini‑programs—createAnimation, this.animate, and CSS3—provides detailed code examples, shows how to integrate Animate.css, and explains using Taro’s page‑scroll and IntersectionObserver techniques to sequence entrance, emphasis, and exit animations.
This article explains the design and implementation of Taro 3.2’s style adaptation for React Native, covering the architectural changes, code transformation process, handling of platform‑specific style differences, preprocessing support, validation mechanisms, and future optimization directions.
The Haro Mobility front‑end team tackled the challenge of maintaining three separate mini‑programs by adopting Taro 3.0 and a custom Babel‑based converter, cutting development effort from 127.5 person‑days to a month of work with four engineers and achieving a 1.4× productivity gain.
This article details the background, design choices, runtime architecture, code transformation, entry and page support, lifecycle handling, and integration strategy of adapting the Taro 3 framework to run on React Native, providing a comprehensive guide for cross‑platform development.
This article details how the Taro team optimized the 京喜拼拼 mini‑program by identifying performance bottlenecks, applying best‑practice coding patterns, refining virtual list handling, reducing setData overhead, and integrating native components, ultimately achieving smoother scrolling and higher experience scores across devices.
This article describes the motivation, product design, core features, and technical implementation details of a simplified Juejin mini‑program built with Taro 3, covering markdown rendering, virtual list handling of large content, and canvas‑based share image generation for a better user experience.
The 2020 China Open‑Source Annual Report highlights Taro’s rapid rise to the fourth‑ranked open‑source project, showcasing its cross‑platform capabilities, active community, industry collaborations, and extensive real‑world deployments that illustrate why it stands out among China’s top five projects.
This article chronicles the evolution of the Taro framework from its inception as a React‑based mini‑program solution to a fully open, plugin‑driven multi‑platform architecture, highlighting technical challenges, Babel‑driven JSX compilation, component model redesign, and community‑driven growth.
This article details how a real‑world property‑listing project leveraged Taro 2.x to build a single codebase that runs on React Native, various mini‑programs, and H5, describing the motivations, technical obstacles, framework comparisons, custom CLI patches, conditional compilation techniques, and deployment workflows.
This article chronicles the evolution of Taro IDE—from a cross‑platform mini‑program framework to an integrated development environment built on Electron and Theia—detailing its architecture, debugging tools, user‑feedback lessons, and the transition toward the Tide IDE framework for scalable frontend engineering.
This article describes how the 58‑rn project extends the Taro 3 framework to support React‑Native with zero‑cost adaptation, detailing architectural changes, Metro bundling, new components and APIs, development workflow, upgrade steps, future plans, and community collaboration.
This article explains the RFC that adds React Native support to Taro 3, covering the motivation, design summary, compilation‑bundle overhaul, runtime adaptations, API and component extensions, app integration options, known limitations, and migration steps for developers.
This article details the design and implementation of Taro 3's React Native support, describing the motivation, compilation and runtime changes, package updates, API and component adaptations, app integration strategies, known limitations, and migration guidelines for developers building cross‑platform applications.
This guide walks through using Vue3’s Composition API, Teleport, Fragments, script‑setup, and style‑vars within Taro, covering installation, project setup, code examples for each feature, build commands, and compatibility notes for both H5 and mini‑program targets.
The article reviews Vue 3's official release, explains the Teleport feature for rendering content outside component trees, introduces the lightweight vue‑lit library for building Web Components with Vue's reactivity, and highlights related graphics experiments, legacy version comparisons, and Taro integration for mini‑program development.
This article details the development of a multi‑platform mini‑program using the Taro framework, covering project background, architecture, technology selection, TypeScript practices, MobX state management, API service encapsulation, image scaling, and canvas‑based poster sharing, with code examples and implementation insights.
This article explains a practical solution for developing, configuring, and packaging multiple mini‑programs from a single codebase using Taro, covering the challenges of cross‑team collaboration, environment‑specific configuration, adaptation layers, and integration methods such as plugins and sub‑packages.
This presentation details the motivations behind rebuilding Taro, introduces the Taro Next architecture and its new capabilities, walks through practical development steps, explains underlying rendering principles for both mini‑program and H5 targets, and outlines performance optimizations and future directions.
This article examines the evolution of WeChat mini‑programs, compares native syntax with progressive enhancement, compile‑time conversion and runtime frameworks, and offers guidance on selecting the most suitable approach based on performance, syntax flexibility, and business needs.
This article details how the 58 Anjuke front‑end team transformed their multiple mini‑programs into a unified, platform‑based architecture using Taro, describing the challenges, design decisions, code‑level configurations, performance optimizations, and the resulting improvements in development efficiency and user experience.
This guide explains how Taro developers can instantly enable eight automatic, zero‑code data‑tracking events and custom analytics in WeChat mini‑programs by integrating Tencent YouShu via a one‑click template, CLI commands, and SDK configuration.
Taro 3 introduces full cross‑framework support for React, Nerv, Vue 2/3 and jQuery‑like APIs, expands to major mini‑program platforms and H5, adds an open plugin system, prerendering, faster builds, CSS‑in‑JS via linaria, virtual list components and a seamless WeChat‑to‑React/Vue conversion tool.
The Taro Next Beta and RC releases introduce H5 compilation, seamless conversion of WeChat mini‑programs to React or Vue, a robust HTML rendering API, CSS‑in‑JS via Linaria, a built‑in VirtualList component, plugin support, and an RFC‑driven path toward a stable version.
The article presents 58.com’s approach to rapid multi‑endpoint development by employing several cross‑platform frameworks—including WubaRN (a ReactNative wrapper), Hybrid, Tangram for layout dynamization, Baidu mini‑programs, Flutter, and the Taro transpilation framework—detailing their architectures, advantages, limitations, and future planning for unified mobile solutions.
This guide explains the background of JD mini‑programs, introduces the Taro multi‑platform framework, and provides detailed installation, project creation, build commands, debugging steps, and an example conversion to help developers efficiently create JD mini‑programs.
This article evaluates Taro’s conversion to JD mini‑programs by comparing package size, long‑list rendering benchmarks, and development experience against native JD and WeChat mini‑programs, revealing where Taro excels, where it lags, and the optimizations it provides.
This article details comprehensive techniques for optimizing the performance of WeChat Mini Programs, covering metrics definition, Taro framework usage, code and asset reduction, rendering improvements, memory management, and real‑world results from the 京喜 homepage, providing actionable guidance for developers.
This article details how JD’s JX mini‑program team tackled massive user traffic by defining user‑centric performance metrics, leveraging the Taro framework, optimizing startup, rendering, network requests, resource handling, component design, and memory usage to dramatically improve first‑screen speed and overall stability.
This article presents a practical Taro‑based architecture that enables a single codebase to be built, configured, and packaged for multiple mini‑programs across different teams, covering configuration, adaptation, conditional compilation, and integration methods such as plugins, sub‑packages, and independent releases.
This article explains the motivations behind Taro 2.0’s CLI overhaul, details how the custom build system was replaced by Webpack, provides step‑by‑step migration instructions, showcases new hooks, loader and plugin configurations, and outlines future plans for the framework.
The article explains how startups can quickly create low‑cost, lightweight multi‑platform e‑commerce applications by combining Tencent Cloud's cloud development services with the Taro framework, covering challenges, concepts of low‑cost and light‑mode, setup steps, and a real‑world example.
Taro is a React‑based framework that lets developers write a single codebase to create mini‑programs for multiple platforms—including WeChat, Alipay, Baidu, and more—as well as H5 and native apps, dramatically reducing development effort and increasing efficiency.
After the 2022 Double‑11 event, JD’s JinxI platform faced fragmented H5, mini‑program, and RN codebases, prompting a comprehensive redesign that standardized the tech stack with Taro, streamlined multi‑platform development, integrated custom build pipelines, and applied performance optimizations such as image handling, API aggregation, and caching.
The article explains how Taro's fast‑evolving 1.x series led to a disruptive redesign of its CLI, replacing the custom build system with webpack in version 2.0, and outlines the resulting maintenance, stability, and extensibility benefits along with upgrade guidance.
This guide highlights the ten most popular Taro material market resources, covering component libraries, skeleton screens, project scaffolds, list views, multi‑platform examples, and utility libraries to help developers accelerate cross‑platform app creation.
This guide explains how to set up the development environment and debug WeChat mini‑programs using the official developer tools, covering native, WePY, Taro, and mpvue frameworks with step‑by‑step instructions, command examples, and visual screenshots.
The article explains how to create a WeChat Mini Program backend with Tencent Cloud development, use the React‑based Taro framework to build a Japanese sentence helper, consolidate multiple cloud functions via tcb-router, and scrape example sentences with superagent and cheerio, highlighting setup tips and known limitations.
This article explains how Taro's H5 build size was dramatically reduced by applying dead‑code elimination, configuring sideEffects, converting component and API packages to ES modules, and using webpack's tree‑shaking together with a custom Babel plugin to replace default imports with named imports.
This article explains how the Taro multi‑platform framework reduced its H5 bundle from over 450 KB to about 96 KB by applying dead code elimination, configuring sideEffects, converting core packages to ES modules, and using a custom Babel plugin to transform default imports into named imports.
Taro 1.1 introduces Baidu and Alipay mini‑program support, new platform identifiers, UI‑library packaging capabilities, numerous bug fixes and API enhancements across WeChat, H5 and React Native, and opens a beta for mini‑program‑to‑Taro code conversion, with detailed commands and future plans.
The article announces the official 1.0.0 release of the Taro multi‑terminal development framework, detailing its evolution from early versions, new component architecture, extensive mini‑program ecosystem support, performance optimizations, richer JSX and TypeScript capabilities, React Native conversion, UI library improvements, and a comprehensive roadmap for future features.
This article details how JD's shopping mini‑program category page was incrementally refactored using the Taro multi‑platform framework, describing the mixed native/Taro development approach, project initialization, configuration tweaks, page implementation differences, performance improvements, and the broader benefits of adopting Taro for cross‑platform development.
Taro UI is a multi‑end UI component library built by the Aotu Lab, offering easy installation, rich components, and seamless adaptation across WeChat mini‑programs, H5, and ReactNative, with detailed quick‑start instructions and code examples for developers.
This article explores the challenges of developing WeChat mini‑programs, examines Taro’s origins, and explains how it leverages React‑like syntax and compilation techniques—using Babel and AST transformations—to convert JSX into mini‑program templates, enabling a write‑once‑run‑anywhere cross‑platform development workflow.
This article examines the evolution of WeChat Mini Programs, the challenges they pose for front‑end developers, and how the Taro framework leverages JSX compilation, Babel‑based AST transformations, and cross‑platform component standards to enable React‑style development across multiple platforms.