I've officially moved T3 Chat off of NextJS and onto TanStack Start.

Thank you DNSimple for sponsoring! Check them out at: https://soydev.link/dnsimple

Want to sponsor a video? Learn more here: https://soydev.link/sponsor-me

Check out my Twitch, Twitter, Discord more at https://t3.gg

S/O Ph4se0n3 for the awesome edit 🙏

T3Dotgg's resource offers insights, tutorials, and resources for gamers and esports enthusiasts. Readers can learn about gaming news, esports events, and professional gaming strategies. With articles, reviews, and interviews, T3Dotgg provides  guidance and expertise for staying informed and competitive in the world of gaming.

Theo - t3․gg

A detailed account of migrating T3 Chat from Next.js to TanStack Start, driven by technical requirements rather than framework dissatisfaction. The original Next.js setup involved hacking React Router into Next.js for a client-first experience, which worked but wasn't sustainable. After exploring multiple alternatives (Remix, Vite+Hono, Cloudflare Workers), the team chose TanStack Start for better client-side routing, frontend-backend synchronization, and team ownership. The migration required 14,000 lines added and 10,000 removed, plus patching TanStack Start itself and moving API routes to Nitro to handle scaling issues. The move wasn't about Next.js being bad, but about finding a framework that better matched their specific needs for a fast, client-focused chat application while keeping frontend and backend deployments synchronized.

I moved off of Next.js

Another “I’m dumping Next.Js” click-bait.

I will never use it. Follow me for more life hacks.

it’s hard to think to migrate all the code from next to tan stack.
it’s like the problem solved on another framework, the time and effort much better to migrate than finding solution on nextjs.
this solution should only used when nextjs cannot be fixed because their infrastructure or something.

I’ve follow this video explain about Tanstack and I dislike it.