Repository navigation
Enable RSC Framework Mode - #259
Open
brookslybrand wants to merge 2 commits into
Open
brookslybrand wants to merge 2 commits into
brookslybrand wants to merge 2 commits into
Conversation
brookslybrand
added this pull request to stack #260
October 8, 2026 14:07
brookslybrand
force-pushed
the
rsc-framework-minimal
branch
from
October 8, 2026 17:02
79e561a to
bb21bba
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This turns on React Router 8.4's unstable RSC Framework Mode with as few changes as possible. No page components were changed. They all still render the way they did before. The server component work is in #258.
What changed:
@vitejs/plugin-rscand newentry.rsc.tsx/entry.ssr.tsxfiles, replacingentry.server.tsx.server.tsnow hands requests to the RSC build's fetch handler.<Scripts />from the root layout and droppedsplitRouteModulesfrom the config, since RSC mode doesn't support either.getColorSchemeand theColorSchemetype intocolor-scheme/utils.tsso the server action doesn't import from a"use client"file..mdURLs still return raw Markdown.<Await>foruse()on the homepage stats.<Await>doesn't handle RSC promises yet, so the stats were never server-rendered and the browser logged hydration errors.Everything else should work the same as before: middleware, caching, waiting for full content for bots, the stream timeout, error logging, SRI, and
.serverimport protection. I smoke tested a production build: homepage, docs, the brand page,.mdURLs, HEAD requests, and the theme toggle.RSC Framework Mode is still unstable. #237 was useful background, but where it differed from the 8.4 RSC docs I followed the docs.