Repo brief: facebookexperimental/Recoil

Generated by RepoPilot · document generated 2026-08-04 · concise human review Evidence snapshot · analyzed 2026-08-04T17:52:31.700Z · commit c1b97f3a0117

Verdict

Mixed — Stale — last commit 2y ago

• 34+ active contributors
• Distributed ownership (top contributor 11% of recent commits)
• MIT licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

Recoil is an experimental state management library for React that provides atoms (primitive state units) and selectors (derived state) as an alternative to Redux or Context API. It solves React's built-in state limitations by enabling fine-grained reactivity, async state handling, and time-travel debugging—all with first-class React Hooks integration and minimal boilerplate. Monorepo layout: core Recoil logic in root packages/, extended tools in packages-ext/ (recoil-devtools is a Chrome DevTools extension; recoil-relay and recoil-sync are sibling packages with separate CHANGELOG files). Main build outputs: cjs/, es/, native/, umd/ directories generated by scripts/build.mjs. Flow types and…

Start here

Open these first:

• package.json — Monorepo root defining build targets, dependencies, and publish configuration for Recoil and related packages.
• babel.config.json — Transpilation configuration required to build Flow-typed source into multiple output formats (cjs, es, umd, native).
• jest.config.js — Test runner setup for the entire monorepo; all contributors must understand how tests are discovered and executed.
• packages-ext/recoil-devtools/src/pages/Popup/PopupApp.js — Root component of the Recoil DevTools browser extension, orchestrating state inspection and transaction replay.
• packages-ext/recoil-devtools/src/utils/Connection.js — Bridge between DevTools UI and the instrumented Recoil app; critical for debugging state changes.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/facebookexperimental/Recoil.git
cd Recoil
yarn install
yarn build
yarn test

Daily commands:

yarn build        # Compiles to umd/, es/, cjs/, native/
yarn test         # Runs jest on all packages/*
yarn flow         # Type-checks with Flow
yarn lint         # ESLint validation
yarn relay        # Relay compiler (required before test)

Note: yarn relay must run before tests due to GraphQL schema compilation.

Key cautions & unknowns

• Stale — last commit 2y ago
• 1. relay-compiler must run before tests: yarn relay compiles GraphQL schemas; yarn test will fail silently without it. 2. Flow type stripping required: @babel/plugin-transform-flow-strip-types must run or…
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.