Handle RSC reload document responses#15032
Conversation
|
Hi @agcty, Welcome, and thank you for contributing to React Router! Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once. You may review the CLA and sign it by adding your name to contributors.yml. Once the CLA is signed, the If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at hello@remix.run. Thanks! - The Remix team |
21c92b0 to
c3a52d7
Compare
c3a52d7 to
59e1713
Compare
|
Leaving a note on direction: the version source for this draft should likely come from the lower-level plugin-rsc primitive in vitejs/vite-plugin-react#1223. This React Router PR is still useful as the framework recovery layer: it wires version propagation through RSC navigations, route discovery, and server actions, and teaches the browser to recover from a 204 + X-Remix-Reload-Document response without trying to decode an empty RSC payload. The part I would expect to change before this is ready is the provisional random React Router RSC version. Once plugin-rsc exposes virtual:vite-rsc/compatibility-manifest, React Router can consume compatibilityManifest.compatibilityVersion and compose it with any React Router-specific deployment/routing state. That keeps plugin-owned build/RSC compatibility in plugin-rsc, while React Router owns the request protocol and recovery behavior. |
|
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
Summary
Validation