What problem does it solve? Enabling the React Compiler in a Rango app is confusing because @vitejs/plugin-react v6 removed its internal Babel path, the new native compiler option depends on a fast-moving optional peer (oxc-transform-react), and server components are silently never compiled. This Skill provides the exact install, wiring, verification, and troubleshooting steps. ## Core Features & Use Cases - One-flag setup: Wire react({ compiler: true }) into both default and Cloudflare Rango Vite configs with correct plugin ordering. - Client-only contract explained: Clarifies why SSR/RSC environments are not compiled and how to verify it with bundle markers like react.memo_cache_sentinel. - Troubleshooting table: Diagnoses unmet-peer/ERESOLVE errors, dead react({ babel }) configs, silent logDiagnostics, and React version targeting issues. - Use Case: A developer upgrades to @vitejs/plugin-react 6.1, hits an ERESOLVE on oxc-transform-react, and uses this Skill to pin the correct peer range and confirm the compiler ran in the production client bundle. ## Quick Start Enable the React Compiler in my Rango app's vite.config.ts and verify it actually compiled the client bundle.