## Problem Current RSC docs describe happy-path setup, but they do not have a consolidated troubleshooting section for the most common setup/runtime failures. As RSC adoption grows, users need fast diagnosis guidance without digging through PRs/issues. ## Proposal Add an **RSC Troubleshooting** section to docs with a symptom -> cause -> fix matrix. Include at least: 1. `TypeError: serverWebpackConfig is not a function` (legacy webpack export mismatch). 2. Missing `rsc_payload_route` / payload endpoint 404s. 3. Missing `'use client'` on interactive components (link #2394 and #2405 context). 4. React version mismatch (RSC currently supports React 19.0.x in RoR Pro). 5. How to verify boundary behavior (server component JS not shipped; client component JS shipped). ## Acceptance Criteria - RSC docs have a troubleshooting page or section linked from main RSC docs. - At least five concrete failure modes are documented with actionable fixes. - Includes quick diagnostic commands/checks where possible. - Cross-links to relevant open issues for deeper context (#2394, #2405).
Problem
Current RSC docs describe happy-path setup, but they do not have a consolidated troubleshooting section for the most common setup/runtime failures.
As RSC adoption grows, users need fast diagnosis guidance without digging through PRs/issues.
Proposal
Add an RSC Troubleshooting section to docs with a symptom -> cause -> fix matrix.
Include at least:
TypeError: serverWebpackConfig is not a function(legacy webpack export mismatch).rsc_payload_route/ payload endpoint 404s.'use client'on interactive components (link Improve error messages when interactive component is missing 'use client' with RSC enabled #2394 and Docs: Clarify distinction between .client/.server file suffixes and 'use client' RSC directive #2405 context).Acceptance Criteria