Turbopack is now stable for `next dev` in Next.js 15, delivering up to 76% faster cold starts and sub-200ms HMR compared to Webpack. This guide covers enabling Turbopack in new and existing projects, migrating custom Webpack configurations (loaders, path aliases) to the new `turbopack` key in `next.config.js`, benchmarking performance with shell scripts, handling unsupported Webpack plugins, troubleshooting common issues like module-not-found errors and styling breakages, and adjusting CI/CD pipelines. Production builds (`next build --turbo`) remain experimental, so the recommended approach is Turbopack for development and Webpack for production until full stability is reached.
Table of contents
Table of ContentsWhat Is Turbopack and Why It MattersEnabling Turbopack in Your Next.js 15 ProjectBenchmarking the Speed WinsConfiguring Turbopack for Your StackProduction Readiness: Where Turbopack Stands TodayTroubleshooting Common IssuesComplete Implementation ChecklistSummary and Next Steps1.4K Impressions