Using Remix, the wrong ? way
summary
A real project moves off Remix data/actions onto React Query and React Hook Form by wrapping sections client-only, creating a Remix-agnostic API, and seed client cache with client loaders so components read from React Query instead of loaderData. Actions become client mutations calling that API and use selective cache invalidation instead of Remix’s all-at-once revalidation. Result: finer invalidation and reusable data but more race conditions, lost default progressive enhancement, and careful sync of redirects and SSR where still needed.
AI-written summary · about
chapters (6)
- 0:00Introduction to the project
- 3:09Understanding Remix core
- 9:26Challenges of scaling
- 14:54Incremental migration strategy
- 20:35Outcomes of the migration
- 23:37Conclusion and key lessons
related talks
26mThe Ultimate Full Stack Framework for 2024: Remix
25mFast Backends for Faster Frontends with Remix
13mReact Remixed
48mReact Remixed
14mRemix run - new kid on the block, and is it a competition for Next.js and Gatsby?
45mWhy I want to do only projects with Remix
20mRemixing How We Give
41mRemix, the hottest JavaScript framework as of today