What problem does it solve? Developers migrating to or working with Turbopack in Next.js 16 face configuration changes, webpack loader incompatibilities, CSS ordering differences, and build failures that are hard to diagnose without bundler-specific expertise. ## Core Features & Use Cases - Configuration Guidance: Set up top-level turbopack config in next.config, including resolveAlias, resolveExtensions, and custom rules for loaders like @svgr/webpack. - Webpack Migration: Map common webpack loaders (css-loader, sass-loader, file-loader, raw-loader) to Turbopack built-ins or equivalents, and know when to fall back to webpack. - Build Diagnostics: Troubleshoot production build failures, oversized bundles, environment boundary errors, and profile HMR or builds with NEXT_TURBOPACK_TRACING. - Use Case: You upgrade to Next.js 16 and your build breaks because of an old experimental.turbopack block and a custom webpack SVG loader. This Skill walks you through moving config to top-level turbopack and rewriting the loader as a turbopack.rules entry. ## Quick Start Ask the assistant to migrate your next.config webpack customizations to Turbopack top-level config for Next.js 16.
