justjavac/awesome-wechat-weapp
Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.
justjavac/awesome-wechat-weapp
A highly popular Chinese-language curated resource list for WeChat Mini Program development. The repo is a single-README collection, not an implementation project: it aggregates official docs, tools, plugins, components, and demos, with very active historical community contribution and occasional updates as recently as 2025-11-19.
Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.
Choose a fork to inspect
Prefer upstream unless you specifically want the older curated snapshot or plan to revive the fork as a branded resource site. For most adopters, this fork is too stale and misses too much modern ecosystem coverage to be the primary choice.
Prefer upstream unless you specifically need this fork's older example-oriented edits or historical snapshot. For adopters, the main tradeoff is that this fork is much older and misses most of upstream's later resource additions.
Choose this fork only if you want a lightweight, frozen 2016 snapshot or a base for your own curation. For practical adoption, upstream is clearly better because it is far more current and actively maintained.
Prefer upstream unless you specifically want an older frozen copy. This fork adds no visible capabilities and is far behind on curation, so it is mostly useful as archival material rather than as a better adopter choice.
Prefer upstream unless you specifically want the wxappfans-branded, early snapshot with a few extra community/tutorial links and are comfortable with substantial staleness.
Prefer upstream unless you explicitly want an old frozen snapshot. This fork adds no visible functionality and is materially behind on curation, so adopters should expect outdated references.
Choose this fork only if you want the early curated list plus a small site wrapper and do not care about modern Mini Program tooling. For current adopters, upstream is clearly the better base.
Prefer upstream unless you intentionally want an old, unchanged snapshot; this fork adds no observable value and is materially behind current curation.
Choose upstream if you want the most current WeChat Mini Program resource index. Choose this fork only if you specifically want a frozen, unmodified snapshot and are prepared to maintain updates yourself.