enaqx/awesome-react
Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.
enaqx/awesome-react
`enaqx/awesome-react` is a large, actively maintained curated link collection for the React ecosystem. It is not an app or library implementation; it is a README-driven resource index covering React, React Native, and related tooling. With 72,581 stars, 7,546 forks, and recent commits on 2026-03-27, it looks like a high-visibility reference repo where forks would mainly be interesting if you want to curate a customized list or track ecosystem resources.
Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.
Choose a fork to inspect
Choose this fork only if you want a dated but runnable React learning starter with examples. Choose upstream if you want an up-to-date ecosystem index and active curation.
Choose this fork only if you want an older, self-contained snapshot to customize. If you want current React ecosystem coverage, upstream is the better base.
Prefer upstream unless you specifically want a frozen 2022 snapshot. This fork does not add capabilities and is far behind, so it is a poor choice for anyone using the list as a current React reference.
Choose this fork only if you want an old example-focused React teaching repo. Choose upstream if you want an actively maintained React ecosystem resource index.
Choose upstream unless you explicitly want a stale snapshot; this fork adds no visible value and is materially behind current maintenance.
Prefer upstream unless you explicitly want an old snapshot. This fork has no visible fork-specific additions and is far behind, so it is mainly useful as an archival starting point, not as the best current React resource index.
Choose this fork only if you want the added example playground and are comfortable with an old snapshot of the project. If you want current React ecosystem curation, upstream is the better fit.
Choose this fork if you want a teaching-oriented, example-rich snapshot of React rather than the actively maintained upstream resource index. If your goal is current recommendations or modern tooling coverage, upstream is the better default.
Choose this fork only if you want a customized, offline-maintained React resource index and do not care about staying current with upstream. If you want the latest curated ecosystem list, upstream is the better choice.