AI summary by TwinMind

I Was Wrong About React Router.

Theo - t3․gg

19m 5s

Previous Video Context and Correction

  • Made controversial video "The End of React Router" few weeks ago
  • Prediction was very wrong - React Router not dying
  • React Router used in 6 out of 10 React applications (possibly more)
  • React Router "as dead as jQuery or Laravel" - actually less dead with exciting developments
  • Thing that died was Remix, not React Router
  • React Router becoming new version of Remix

Core Team Discussion Setup

  • Multiple Remix core team members present including Pedro, Ryan Florence
  • Decision to kill/merge Remix made just days after previous video
  • Remix team sacrificing brand to push React ecosystem forward
  • Ryan Florence wrote comprehensive blog post explaining changes

React Router v6 to v7 Transition

  • v6 to v7 will be non-breaking upgrade
  • Vite plugin for Remix coming to React Router in v7
  • Vite plugin makes existing React Router features more convenient (not required)
  • v7 supports both React 18 and React 19
  • Remix v3 becomes React Router v7
  • Remix v2 to React Router v7 will be non-breaking upgrade

New Features in React Router v7

  • Server components
  • Server actions
  • Static pre-rendering (previously required spinning up server and caching HTML)
  • Type safety across the board
  • Addressing gaps that newer routers like TanStack Router were created to fill
  • Better behaviors for dynamic applications, query params

Remix Background and Evolution

  • Originally template for "right way" to do React apps by React Router creators
  • Built custom bundling solution due to poor webpack story for server/client splitting
  • Went all-in on ESBuild before Vite existed
  • Most of Remix was pile of things on top of ESBuild
  • Pedro and Mark Dalgleish ported everything to Vite in ~2 months (expected to take months/years)

Vite Integration Benefits

  • 10x faster HMR compared to previous ESBuild setup
  • 5x faster HDR (Hot Data Revalidation)
  • 90x faster HMR for shop.app (Shopify mobile app)
  • Remix now just a Vite plugin
  • Can use other Vite plugins alongside (React compiler, Tailwind, etc.)
  • No longer need custom Remix-specific plugins

Technical Architecture Changes

  • Remix now just Vite plugin that makes React Router more convenient
  • Outside plugin, Remix mostly re-exports React Router
  • No technical purpose for splitting code/docs/issues between two projects
  • Artificial overhead and user confusion eliminated

Server Components Strategy and Impact

  • Server components are the future of web development
  • Average React dev doesn't use Next.js or host React on server
  • Most React devs using old Create React App setups with hundreds of contributors
  • Server components require starting at route level (unlike hooks which could be adopted incrementally)
  • React Router path enables server components adoption for large existing codebases
  • Companies like Twitch could realistically adopt server components through this path

Historical Context - Hydrogen and Server Components

  • Hydrogen v1 by Shopify was first server component framework (not Next.js)
  • Ran server components in production for years
  • Not happy with early results due to sketchy early implementation
  • Had client.ts and server.ts files initially
  • Hydrogen v2 moved away from server components
  • Shopify acquired Remix team, allowing growth and better direction

Future Remix (Codename: Reverb)

  • Internally codnamed "Reverb"
  • Engineer quote: "wow that's really beautiful"
  • Very different model from current Remix
  • Different enough to warrant separate name initially
  • Enables incremental adoption by running both versions in parallel
  • Keeps Remix brand/community/ethos for future

Server Components Demo and Implementation

  • Demo showed moving from loader returning data + useLoaderData hook
  • To loader returning JSX directly (server component)
  • Server renders HTML, client doesn't manage with JavaScript
  • Can mount client components (like Carousel) within server components
  • Treats JSX same way as other data
  • Product isn't component so can't pass children - treat as data
  • 70-80% of server component functionality vs Next.js 100%
  • Much easier to jump into than full server component model

Technical Implementation Details

  • All built on RSC (React Server Components)
  • Supports suspense and streaming (had streaming before other frameworks)
  • Can use defer with suspense wrapping
  • Arguments come from route, not passed to loader
  • Can return async components from separate files
  • Async JSX implementation challenges noted

TwinMind

Get summaries like this for your own meetings

TwinMind takes notes in the background during meetings, lectures, and calls, then writes the summary for you.

Free plan to get started

No bot joins your calls

Phone, desktop & Chrome apps

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome