We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2
1–10 of 230 posts
Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2
#2Reminder, as its not mentioned:
Next.js is produced by Vercel, a competitor to Railway.
Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2
#3It’s absolutely mind boggling to me that we have gotten to a point that building a web frontend takes longer than compiling the Linux kernel..
Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2
#4Reminder, as its not mentioned: Next.js is produced by Vercel, a competitor to Railway.
Moving to vite + tanstack builds faster is also a fact.
Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2
#5Incredible that the builds were ever 10min. How far things have regressed.
Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2
#6This is one of the most frustrating thing about working with NextJS. There seems to be no way to improve the speed of building the app.
Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2
#7We went through a very similar migration. Had a Next.js landing page and a separate TanStack Router SPA - consolidated both into a single Vite + TanStack Start app. Same experience with build times and the architecture mismatch: our app is heavily client-side with real-time state, and fighting Next.js's server-first assumptions wasn't worth it. TanStack Router's type-safe routing and file-based route generation have been great.
Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2
#8It’s absolutely mind boggling to me that we have gotten to a point that building a web frontend takes longer than compiling the Linux kernel..
As a non-frontend developer mainly observing and touching something here and there, a lot of the things that frontend developers do seem vastly over-engineered.
Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2
#9It’s absolutely mind boggling to me that we have gotten to a point that building a web frontend takes longer than compiling the Linux kernel..
As a non-frontend developer mainly observing and touching something here and there, a lot of the things that frontend developers do seem vastly over-engineered.
I'm not insanely deep into frontend, I mostly just pick up React and call it a day, but it seems like this is also over-engineered?
I've seen vanilla JS before, and I just know I wouldn't want to do the housekeeping that comes with it. People claim it's less work because it' simpler, but I fully expect myself to rewrite the thing at least twice, only to give up because I have no actual mental model anymore of how it works.
Re: We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2
#10I have a Nextjs heavy app which takes around 7 minutes currently. But I've been thinking of moving away from next for a long time now. TanStack seems to be a good fit. This gives me a bit more confidence in just doing it.