Discofork
Repository brief

facebook/react-native

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-29T22:11:09.142Z
3mo ago

facebook/react-native

facebook/react-native is the main upstream React Native framework repository. It is active, heavily used, and still receiving frequent commits as of 2026-03-29. Forks are most interesting if you care about mobile app infrastructure, native platform integration, or contributing back to the core ecosystem.

GitHub
Loading tags...
Stars125,681
Forks25,125
Default branchmain
Last pushed2026-03-29T13:52:34Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs
Selected

Choose this fork if macOS is the target product and you need React Native behavior tuned for desktop UI conventions. Stay with upstream if you mainly want the newest cross-platform React Native changes with the least maintenance burden.

Choose this fork if visionOS is the product target and you want React Native with platform-specific support already baked in. Stick with upstream if you need the broadest compatibility, fastest access to new React Native releases, or minimal divergence risk.

Choose this fork if you are building in the Expo ecosystem and want Expo-specific runtime, engine, and build tooling already baked in. Avoid it if you want close upstream parity, easier React Native upgrades, or a minimal customization surface.

Choose this fork only if you need its Discord-specific internal tooling and deep React Native customizations. If you want a broadly current, low-maintenance React Native base, upstream is the safer choice.

Prefer this fork only if you must preserve an old, customized React Native stack and can accept major maintenance debt. For new work or active modernization, upstream React Native is the better default.

Choose this fork only if you need its custom modifications and are willing to own long-term maintenance. If you want current React Native behavior, ecosystem compatibility, and lower upgrade risk, upstream is the safer default.