AI summary by TwinMind
React Router V7 just dropped, here's why you should care
Theo - t3․gg
29m 10s
Personal React Router History
- Speaker has complex relationship with React Router over the years
- Used extensively at Twitch for routing architecture and internal tools
- Major frustrations with query params implementation and terminology
- Previous issues: lack of type safety, limited server rendering options
- Many problems now fixed in V7
React Router V7 Significance
- Described as "one of the most important releases in react history"
- Enables average React devs to access server components benefits
- Represents "effective murder of remix" - scrapping for parts integration
- Remix V3 (not V2) planned for future - very different direction
- V7 bridges gap between React 18 and 19
Epic React Sponsor Segment
- Kent Dodds tutorial platform
- React 19 focused content
- Local development environment (clone repo, run locally)
- Community features: Discord, live participants
- Company training option with boss letter template
- Link: soy.link/epic-react
V7 Release Announcement
- Stable release brings Remix features into React Router
- Remix V2 users encouraged to upgrade to React Router V7
- Positioned as smoothest path for React ecosystem migration
- Acknowledges React Router's majority usage in React apps
- Enables React 19 benefits for large codebases like Twitch
Upgrade Paths and Features
- Framework mode for Remix-like functionality
- V6 upgrade guide available
- Remix migration guide exists
- New features: compiler, Vite support, bundle splitting, type safety, HMR
- Two modes: library-only or full framework
Development Philosophy
- Modular approach vs monolithic frameworks
- Comparison to Next.js constraints
- Better for large enterprise codebases with multiple contributors
- Flexibility to opt out of framework decisions
- Not best for majority of apps, but crucial for large revenue-generating apps
CLI and Templates
- Create React Router CLI tool
- Built-in deployment pipelines
- Docker support (separate files for bun, pnpm, no yarn)
- Vercel, Cloudflare Workers, Netlify support
- Vite integration as default
Code Structure Analysis
- Magic exports concern - unclear entry points
- Comparison to clear config-based routing
- Missing index.html clarity
- Framework vs library export options
- Generated types in visible directory (requires dev server running)
Server-Side Rendering Demo
- SSR working with streaming updates
- HTML pre-rendered and sent to browser
- Streaming context and data loading
- Express server integration
- Load context and loader functions
Streaming and Suspense Features
- Async data loading with promises
- Suspense boundary integration
- Fast static parts, slower dynamic parts served separately
- Streaming HTML responses
- 5-second default timeout for streams
Technical Concerns
- Mixed client/server code in same files
- Traditional SSR model (code runs on both client and server)
- Tree shaking dependency on compiler correctness
- Server-only imports require careful handling
- Missing server components file separation
Configuration Challenges
- Hidden files requiring "eject" command
- Magic exports after ejecting
- Stream timeout configuration issues
- Documentation gaps for advanced features
- Deprecated abort delay configuration
Overall Assessment
- Monumental engineering effort
- Supports ~50% of React apps
- Smooth upgrade path for most users
- New features may have rough edges
- Strong recommendation to upgrade from older versions
- Sets up long-term success without Next.js migration pressure
- React Router positioned as stable long-term solution
