Slow development mode with route compilation delays
7/10 HighNext.js dev mode is slow and painful; developers must wait for route compilation when checking multiple routes. The development server consumes several gigabytes of RAM, creating frustrating workflow interruptions.
Sources
- Why Should You Move Off Next.js?
- Svelte Kit doesn't scale well on large projects #13455
- Productive Python development: How to tackle 5 common issues | TechBeacon
- Why Companies Are Moving Away from Next.js in 2025? - Enstacked
- Next.js at refactor or extinct situation.
- What's New in Vite Explained by Its Creator
Collection History
The cold start for `npm run dev` (Vite) takes 1:30 minutes, while the hot restart takes 1 minute. This can lead to discrepancies between server behavior during development and production, which has repeatedly caused bugs.
The unbundled approach actually creates a network bottleneck that makes the server startup quite slow... full bundle mode is specifically designed to solve that problem.
Switching files in a slow editor or jumping between apps on a slow computer is frustrating... I believe these micro delays add up, too. They cost us productivity and cause frustration.
Slow and painful dev mode, if you changed something and need to check more than 1 route, you need to wait till route compiled. Next.js server also uses few gigabytes of RAM.