// the find
react-native-community/directory
A searchable and filterable directory of React Native libraries.
The official directory for React Native libraries, live at reactnative.directory. It's a Next.js site where the canonical source of truth is a single JSON file checked into the repo, scored and enriched with npm/GitHub data via build scripts. Useful primarily for React Native developers choosing between libraries, and for library authors who want discoverability.
The scoring system is open and hackable — it's a plain TypeScript file anyone can submit a PR against, which is the right call for a community-owned metric. Platform compatibility tracking (iOS, Android, Windows, macOS, tvOS, visionOS, HarmonyOS) is genuinely thorough and covers targets most directories ignore. The per-package detail pages go deeper than you'd expect: download charts, dependency tree, version history, and an inline code browser pulled from unpkg. Data refresh is automated via Vercel cron and a GitHub Actions workflow, so the directory doesn't rot the way manually-maintained lists do.
The entire library dataset lives in one `react-native-libraries.json` file at the repo root — adding a library requires a PR, which is a reasonable gate for quality but means the friction is entirely on the submitter and the review queue. The public API is read-only and serves the pre-built `data.json` blob, so if you want to build anything that queries by specific criteria at runtime you're stuck fetching and filtering the whole dataset client-side. The VS Code extension is a separate repo with its own maintenance burden and it's unclear how well it tracks the main directory's data. New Architecture support detection is automatic but fallible enough that the README dedicates a tip to manually overriding it, which suggests the heuristic gets it wrong often enough to matter.