Moving custom Webpack loaders and aliases to Turbopack's turbopack config and compatibility shims.
Skip to solution
KEEP THE
mediumFrontend
Migrating Webpack config to Turbopack — what breaks?
931 views
01
Understand the problem
turbopackwebpackmigration
02
Attempt it yourself
Sketch your approach before reading the solution — that's what interviews test.
Nudge consolestandby
Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.
03
Study the solution
Most webpack: customizations map to experimental.turbo or turbopack config; Turbopack handles SVGR, Sass, MDX natively but custom plugins that tap Webpack's compiler API still need Webpack.
Solution ready — 2 min read
Classified // press E to declassify
04
Join the discussion
Discussion (0)
Sign in to join the discussion.
No responses yet. Be the first to share what you think.
Transmission complete // awaiting log
KEEP THE
STREAK ALIVE.
Dossier 26 of 95 decoded in the Next.js track. One more won't hurt.