You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, we fetch /react once the client JavaScript is loaded in order to get the RSC response from the server and hydrate the page. This is horribly inefficient, and we should return the RSC response encoded as JSON in a <script> tag along with our SSR response.
For reference, see how Next.js is planning to solve this problem: vercel/next.js#30994
Super clever, and we should be able adopt a similar pattern (or create our own).
The text was updated successfully, but these errors were encountered:
Today, we fetch
/react
once the client JavaScript is loaded in order to get the RSC response from the server and hydrate the page. This is horribly inefficient, and we should return the RSC response encoded as JSON in a<script>
tag along with our SSR response.For reference, see how Next.js is planning to solve this problem: vercel/next.js#30994
Super clever, and we should be able adopt a similar pattern (or create our own).
The text was updated successfully, but these errors were encountered: