dev.to
Next.js at refactor or extinct situation.
Next.js become a hype of the day (or year), but it's slowly suffocating under the weight of technical debt. There are many big enough pain points with Next.js: - 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. Turbopack complaining about perfectly working TS code, and struggle to understand `:global` in CSS modules, still not production ready.
Related Pain Points2件
Turbopack unreliability with TypeScript and CSS modules
7Turbopack, Next.js's replacement bundler, complains about valid TypeScript code and struggles to understand `:global` in CSS modules. Despite these issues, it remains unstable and not production-ready.
Slow development mode with route compilation delays
7Next.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.