Remix Your React Router Applications
summary
A demo migrates a CRA-style React Router v6 SPA to the beta React Router v7 and the V plugin, showing that you can replace react-router-dom with react-router in minutes and opt to stay a library or enable framework features and SSR via a boolean. It converts to file-based routing + loaders/actions, adds server loaders and actions so pages work with JavaScript off, then adds client loaders that hydrate and cache via react-query to restore loading states and toasts; the demo app runs and the progressive enhancement works.
AI-written summary · about
chapters (12)
- 0:00Introduction and background
- 1:53React Router V7 announcement context
- 3:17Client-side vs server-side rendering
- 7:08Progressive enhancement with Remix
- 16:58React Router V7 migration paths
- 19:29Demo setup and library upgrade
- 23:47Switching to file-based routing
- 31:10Type safety with React Router
- 35:21Progressive enhancement in action
- 44:16Handling mutations without JavaScript
- 50:15Progressive enhancement on detail page
- 54:25Migration summary and closing
related talks
10mRouting Reimagined: Upgrading to React Router v7
40mThe Remix Evolution: How React Router v7 Enables Fast and Resilient Apps
26mVanilla React
12mThe React Router take on RSC
52mExploring the World of Remix: A Guide to Building Resilient and Performant Web Apps
55mUse the Platform With Framework Agnostic Routing
54mExploring the World of Remix: A Guide to Building Resilient and Performant Web Apps
10mCRA to App Router in 5 Steps: A Case Study with Graphite