facebook/react-native

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.