Remixing How We Give
summary
Daffy.org migrates a large Next + Rails frontend to Remix and claims concrete wins: run Remix and Next together using an Express proxy, share session state across apps, then flip routes and remove reloadDocument to regain SPA navigation; loaders aggregate multiple API endpoints and transform/localize data; actions simplify mutations and validation so forms work without JS; resource routes generate PDFs and Open Graph images on demand; internal libraries like remix-utils and remix-auth grow from this work and power production resilience.
AI-written summary · about
chapters (15)
- 0:00Daffy and Remix intro
- 1:19Problems with old stack
- 2:23Why Remix for resilience
- 3:49Simplifying form mutations
- 4:53Separation of concerns
- 5:59Next.js to Remix migration
- 7:24Authentication across apps
- 8:31Client-side navigation issues
- 9:40Remix as BFF
- 11:48Component and data patterns
- 13:35Error handling in loaders
- 14:57Custom conventions and types
- 16:21Type-safe API client
- 17:06PDFs and OG images
- 18:10Remix community contributions
related talks
13mReact Remixed
41mRemix, the hottest JavaScript framework as of today
14mRemix run - new kid on the block, and is it a competition for Next.js and Gatsby?
59mRemixing Frontend Development
26mBuilding Better Websites with Remix
45mRemix: the Truly Full-Stack Framework
48mReact Remixed
37mThe Remix Philosophy is not Just for Remix