principlejavascriptModerate
Turbopack: current status and when to enable it in Next.js
Viewed 0 times
Next.js 15, Turbopack stable for dev
turbopacknext dev turbopackrust bundlerincremental buildHMR speed
Problem
Developers enable Turbopack in Next.js expecting full production support and encounter missing features or different behaviour from Webpack.
Solution
As of 2025, Turbopack is stable for development (next dev --turbopack) in Next.js 15+ and works for most projects. Production builds (next build --turbopack) are available but still being hardened. Evaluate feature parity for your specific plugins before fully switching.
// package.json
{
"scripts": {
"dev": "next dev --turbopack",
"build": "next build" // still webpack or --turbopack if stable for you
}
}
// package.json
{
"scripts": {
"dev": "next dev --turbopack",
"build": "next build" // still webpack or --turbopack if stable for you
}
}
Why
Turbopack is a Rust-based bundler with incremental computation built in. It only recomputes the minimal graph of changed modules. This produces faster HMR than Webpack, especially in large codebases where Webpack's JS-based HMR must reprocess whole module graphs.
Gotchas
- Not all Webpack loaders have Turbopack equivalents — check the Next.js docs for supported loaders
- Turbopack config lives in next.config.js under 'experimental.turbo' (key name may change with versions)
- Custom Webpack plugins in next.config.js do not apply when Turbopack is active
- Turbopack generates different chunk names — CI cache keys based on chunk names may need updating
Context
Evaluating or adopting Turbopack in a Next.js 14/15 project
Revisions (0)
No revisions yet.