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
Running Next.js on Turbopack?
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.
What it is
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.
The honest version
No technology is all upside. This is where Turbopack earns its place and where it tends to cause trouble.
Sound familiar?
The Turbopack problems that bring people to us, and what you have once each one is fixed.
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
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
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
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
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
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
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
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
Call us for a single Turbopack crash, or hand us the Next.js app and we will take it from there.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
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
Paste the Next.js version, the config and the panic. A real person replies with a fixed price before anyone touches the repo.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: