Overreacting—From React to Hotwire
summary
A pragmatic hybrid migration keeps the existing React SPA as static assets while new features land in Rails with Hotwire (Turbo, Turbo Frames/Streams, Stimulus) and deployment via Kamal/Docker; authentication uses cookie sessions plus a Turbo-driven localStorage token bridge. The project converts an itinerary builder into CRM modules, embeds React with turbo-mount and iframes for modals, and reports real wins: 50% faster feature delivery, 93% smaller bundles, shared cookie + localStorage auth flow, doubled task throughput.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 2:30Switching React to Hotwire
- 5:18React’s pros and limits
- 7:27React problems: build times
- 9:31AI and dev speed
- 10:59Hotwire’s rise and benefits
- 12:51What is Hotwire
- 13:58Migration to Rails with Hotwire
- 15:26React as static files in Rails
- 16:31Deployment with Kamal and Docker
- 17:37Auth between React and Rails
- 19:44ViewComponent and Rails
- 20:06Results: faster feedback
- 21:51Rails, AI, and productivity
- 22:39Productivity gains quantified
- 23:23Non-React JS libraries
- 24:31Embed React with Turbo Mount
- 25:34Embed Rails in React with iframes
- 26:36Learning Stimulus
- 27:17Gradual migration plan
- 28:02Conclusion and Q&A
related talks
23mReact-ing to Hotwire
31mReact on Rails
09mHotwire Cookbook and common use cases
25m"React integration into existing Rails applications"
21mMigrating critical apps to React
31mReact.js on Rails
36mFront-End Sadness to Happiness: The React on Rails Story
18mReact-ing to Rails: Why Ruby on Rails is the best Stop for Web Developer