facebook/react▌

Run tests for React codebase across multiple release channels and configurations. \n \n Supports six release channels: source (default), experimental, www, www with variant false, stable, and classic, each with distinct feature flag configurations \n Accepts test patterns, watch mode for TDD, and variant flags to test different code paths \n Requires explicit test pattern argument to avoid running the entire test suite; uses --silent flag to surface failures and --no-watchman for sandboxing comp

Automated code formatting and linting to resolve style issues before CI checks. \n \n Runs Prettier for code formatting and linc for lint validation in sequence \n Identifies remaining manual fixes needed after automated corrections \n Prevents CI failures by catching formatting and lint errors before commit \n

Pre-commit validation for React contributions with parallel type checking and testing. \n \n Runs formatting and linting sequentially, stopping on first failure to catch issues early \n Executes type checking and dual test suites (source and www) in parallel using subagents for efficiency \n Accepts optional test pattern argument to filter which tests run \n Provides detailed failure reporting with suggested fixes when any step fails \n

Inspect and compare feature flag states across React release channels. \n \n View all flags across channels (www, www-modern, canary, next, experimental, rn variants) or compare specific channels with --diff \n Output formats include default table view, CSV export, and cleanup status grouping \n Flag states indicated by symbols: enabled (✅), disabled (❌), variant testing (🧪), profiling-only (📊) \n Common pitfall: __VARIANT__ flags are tested in both states on www; use --diff to spot meaningful

Manage React feature flags across channels, gate tests conditionally, and debug flag-specific test failures. \n \n Four flag files control defaults and channel-specific overrides (canary, www, React Native, test renderer) with __VARIANT__ flags simulating gatekeepers tested in both states \n Use @gate flagName pragma to skip tests entirely when a flag is unavailable, or inline gate() to branch assertions when behavior differs \n Adding a new flag requires entries in the main file plus all fork f

Extract and manage error codes for React applications. \n \n Automatically extracts error messages from React source code and assigns unique error codes to new messages \n Detects \"unknown error code\" warnings and flags messages that need code assignment \n Validates that error codes remain synchronized with the current codebase through a simple yarn command \n

Static type checking for React code across DOM and native platforms. \n \n Four renderer options cover standard DOM, browser-specific code, React Native, and Fabric environments \n Run yarn flow with optional renderer argument; use yarn flow-ci for comprehensive but slower checks \n Reports type errors with file locations to help identify and fix issues quickly \n Watch for common pitfalls: missing renderer specification, unexamined $FlowFixMe suppressions, and incorrect type imports \n