All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Railway's Frontend Migration from Next.js to Vite + TanStack Router

By

bundie

1mo ago· 5 min readenInsight

Summary

Railway migrated their entire production frontend from Next.js to Vite + TanStack Router, including their dashboard, canvas, and railway.com website. The migration was completed in just two pull requests with zero downtime. While Next.js served them well initially and helped scale to millions of users, it eventually became unsuitable for their product needs. The article details their migration process, technical decisions, and lessons learned from moving away from Next.js.

Key quotes

· 4 pulled
Railway's entire production frontend no longer runs on Next.js. The dashboard, the canvas, railway.com, all of it now runs on Vite + TanStack Router
Next.js served us well. Then it didn't.
Next.js got railway.com from zero to a production app serving millions of users monthly. It's an excellent framework, but it stopped being the right one for our product
we shipped the migration in two PRs with zero downtime
Snippet from the RSS feed
We migrated railway.com, the dashboard, and the canvas from Next.js to Vite + TanStack Router in two PRs. Here's why, how, and what we learned.

You might also wanna read