Running Next.js on Turbopack?

Turbopack crashing or HMR drifting? We bring it back.

Turbopack is fast when it works and ugly when it does not: a webpack loader the team relied on now warns as unsupported, HMR stops updating a route after a save, or next dev crashes with a Rust panic nobody can grep. We work through the Next.js config, the module graph and the Turbopack options until the dev loop is reliable again.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

turbopack-dev.log

still broken

What it is

Turbopack at a glance

Turbopack is the Rust-based bundler built by Vercel to replace Webpack inside Next.js. It was announced in October 2022 and became the stable bundler for next dev in Next.js 15 (October 2024). The production build with Turbopack reached beta in Next.js 15.3 and continued stabilizing through 2025 releases.

The tool is open source under the MPL-2.0 license, built on the Turbo engine (a shared, incrementally computing core also used by Turborepo), and designed to replace Webpack-style loaders with native Rust modules for TypeScript, JSX, CSS and assets. In practice, teams adopt Turbopack through the next build and next dev flags rather than as a standalone bundler.

Type
Rust-based bundler for Next.js
First released
2022 alpha, 2024 stable dev, 2025 stable build
License
MPL-2.0, open source
Maintained by
Vercel
Typically used for
Next.js dev server, Next.js production builds, fast refresh at large app scale

The honest version

Turbopack pros and cons

No technology is all upside. This is where Turbopack earns its place and where it tends to cause trouble.

Where Turbopack is strong

  • Big win on cold startA Next.js app that took 30 seconds to boot under Webpack now opens in 2 or 3 on the same machine. On an application with hundreds of routes, that reshapes the dev loop entirely.
  • Fast Refresh updates feel instantEdit a component, save, and the browser reflects it before you look up. Bigger apps keep that snappiness instead of degrading into full reloads.
  • Built into Next.js by defaultSince Next.js 15 it is the default dev bundler. No extra tool to install, no third-party plugin to pin, and the upgrade path moves with the framework.
  • Native TypeScript, JSX and CSSLoaders you used to configure for Webpack are replaced by built-in Rust handlers, which cuts the dependency tree and the surface for config drift.
  • Shared incremental coreTurbopack and Turborepo both lean on the Turbo engine, so caching patterns and work splitting feel consistent across the local build and the monorepo pipeline.
  • Production build is maturingBy late 2025 the production path under --turbopack is production-ready for many Next.js apps, with Vercel running it on its own properties as a forcing function.

Where Turbopack bites

  • Webpack plugin ecosystem does not come alongA next.config.js that relied on custom webpack() hooks, MDX remote, next-pwa or a vendor loader will warn, fall back or outright refuse. Migration is on you.
  • Error surface is still roughA Rust panic in a worker thread is not a developer-friendly error. The stack trace can be useful to Vercel, less so to the team trying to ship by Friday.
  • HMR edge cases still appearA full reload where Fast Refresh should have fired, a stale layout on route change, or a server component edit that fails to propagate are all still in the issue tracker in 2025.
  • Only really useful inside Next.jsTurbopack is not a general-purpose bundler you ship libraries with. If you leave Next.js, you leave Turbopack too, which is a very different trade-off from choosing Vite.
  • Observability is thinBuild timings and the module graph are visible, but memory profiling, cache invalidation reasons and detailed dependency tracing are far behind Webpack's long-matured tooling.
  • Compatibility flags drift between releasesThe experimental turbo config, the turbopack top-level key and the module rules shape have changed multiple times. Pinning Next.js matters more than it looks.

Sound familiar?

Common Turbopack problems we fix

The Turbopack problems that bring people to us, and what you have once each one is fixed.

unsupported loader

A Webpack loader is not supported

A SVG loader, a GraphQL loader or a bespoke asset handler that worked under Webpack is either unimplemented or silently ignored, and the pages that needed it now break at import time.

Loaders ported or replaced

thread 'tokio-runtime-worker' panicked

Turbopack crashes with a Rust panic

An input file the Rust worker could not parse, a race on a workspace edit, or a config option interacting with Fast Refresh in an unintended way.

Dev server stable through the day

Fast Refresh had to perform a full reload

HMR keeps falling back to a full reload

A module cycle, a file that exports both a component and a helper, or a hooks-order change that Fast Refresh cannot recover from without starting over.

Edits land without a full reload

Module not found: Can't resolve '@/components/Button'

Path aliases do not resolve

A tsconfig paths entry that Turbopack's resolver interprets differently than Webpack did, or a baseUrl that was never carried across to the newer config shape.

Aliases resolving under both bundlers

the following webpack configuration will be ignored

next.config.js tweaks are silently ignored

A webpack() hook that defined aliases, modified rules or injected plugins, none of which Turbopack honors. The build keeps going; the behavior those tweaks provided does not.

Config moved to the Turbopack shape

ChunkLoadError: Loading chunk failed

Chunk loading fails after a deploy

A client with a cached old manifest requesting a chunk that no longer exists, usually on long-running tabs after a production rollout with aggressive asset hashing.

Deploys survive open tabs

package 'sharp' is not installed

Optional native deps are missing

A production image pipeline that required sharp, or a dependency that expected swc-native to be present, failing at build time rather than at dev.

Native dependencies pinned in CI

cannot define a route with the same specificity

App router conflict surfaces

Two routes under app/ that Turbopack now treats as colliding, usually because of an optional catch-all added alongside a specific segment.

Routes disambiguated, build green

What we do

Turbopack help, from one panic to the whole Next.js setup

Call us for a single Turbopack crash, or hand us the Next.js app and we will take it from there.

Rescue
A dev server that keeps crashing, an HMR loop that goes cold, or a production build that refuses to finish. We stabilize the loop first and explain the cause second.
Webpack to Turbopack migration
Porting next.config.js tweaks, loaders, and aliases onto the Turbopack shape, keeping behavior equivalent instead of just making the warnings disappear.
HMR and Fast Refresh work
Chasing full-reload regressions, breaking the cycles that defeat Fast Refresh, and getting edits back to feeling instant across every route.
Next.js version upgrades
Minor and major Next.js upgrades rehearsed with Turbopack on, including the experimental and stable flag changes that quietly reshape the config between releases.
Production build readiness
Evaluating whether your app is ready for next build --turbopack, fixing whatever is still blocking, and keeping a clean fallback until it is.
Managed Tech
Ongoing Next.js and Turbopack monitoring, upgrade rehearsals, and an engineer on call when a release note understates the impact of a flag flip.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Turbopack alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Turbopack questions

Something else? Call+1 737 727 7327

Should we switch our Next.js app to Turbopack?

For the dev server, almost certainly yes on Next.js 15 and later, because it is the default and the speedup is meaningful. For the production build, it depends on your plugins and loaders. A short compatibility review will tell you whether next build --turbopack is safe today or worth waiting a release for.

Why does our Webpack config no longer apply?

Turbopack ignores the webpack() hook in next.config.js and reads its own turbopack or experimental.turbo section instead. Aliases, module rules and plugin injections all need to be translated. We port them one by one, with a test that proves each original behavior is preserved.

What causes Turbopack Rust panics in dev?

Usually an input the Rust worker cannot parse, a stress from many file saves at once, or an interaction between Fast Refresh and a particular import shape. Capturing the panic log, the Next.js version and the reproducing file is enough for us to either patch the cause locally or file a clean upstream issue.

Why is Fast Refresh falling back to a full reload?

Common reasons are a module that exports both a component and a non-component value, a circular import between two client components, or a component whose hook order changed between edits. Each has its own fix; we trace the exact cause rather than guess.

Can we use Turbopack outside Next.js?

Not in any practical way today. Turbopack is designed around Next.js conventions and the Turbo engine. For general bundling, Vite, esbuild and Rspack are the pragmatic choices. If you are leaving Next.js, Turbopack is not the thing you carry with you.

How much does Turbopack help cost?

The initial estimate is on us. Share the Next.js version, the config and the error, and a quote with a scope lands in your inbox before engineering starts.

Free estimate

Turbopack giving you trouble?

Paste the Next.js version, the config and the panic. A real person replies with a fixed price before anyone touches the repo.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.