NervJS/taro

Choose this fork only if you specifically want an unmodified Taro baseline to maintain yourself; otherwise upstream is the better choice because this fork adds no visible capability and is materially behind on fixes.

Choose this fork only if you want its older H5/runtime customizations and are prepared to maintain a large divergence yourself. If you want the current Taro ecosystem, active fixes, and lower upgrade risk, upstream is the better choice.

Choose this fork only if its Harmony/hybrid and router/cache changes match a concrete product need. If you want an actively maintained, broadly compatible Taro baseline, upstream is the safer choice.

Choose this fork only if you specifically need an older, unchanged Taro snapshot. For most adopters, upstream is the better choice because this fork adds nothing new and is materially behind recent fixes and feature work.

Choose this fork only if you need its legacy behavior or custom changes and are prepared to live without upstream progress. For new work, upstream is the safer choice.

Prefer upstream unless you specifically need this exact frozen snapshot; this fork adds no visible capabilities and is materially behind active upstream.

Choose this fork only if its added H5/server/runner customization is specifically what you need and you are prepared to own a stale, highly divergent codebase. If you want current Taro fixes and active maintenance, upstream is the safer default.

Choose this fork only if you already depend on its custom behavior or bundled tooling. If you want current Taro features, active fixes, and lower maintenance burden, upstream is the better default.