Context: React Compiler 1.0 shipped in October 2025 and is the #1 developer excitement feature (62% in State of React 2025 survey). It automatically memoizes components and eliminates the need for manual `useMemo`, `useCallback`, and `React.memo`. Content SDK's React components have not been tested for compiler compatibility. The compiler enforces the Rules of React strictly -- violations that work in non-compiled mode may break.
Steps:
1. Install `babel-plugin-react-compiler` and `eslint-plugin-react-compiler` in the monorepo root devDependencies
2. Run the ESLint plugin across all packages to identify Rules of React violations
3. Fix any violations found (common issues: mutating props, conditional hook calls, non-idempotent render functions)
4. Add a CI job that builds the test suite with the React Compiler enabled
5. Document React Compiler compatibility in README and CHANGELOG
Acceptance criteria:
All Content SDK React components pass the React Compiler ESLint plugin with no errors
CI includes a React Compiler build job
README documents compiler compatibility status
Risks: Some Content SDK components may rely on patterns that the compiler cannot optimize (e.g., dynamic hook patterns in `withSitecore`). These may need refactoring. The compiler is opt-in per-file, so partial adoption is possible.