turbopack

Migrating webpack loaders to Turbopack involves translating common webpack loader and alias patterns into Turbopack-compatible configuration. This updates your Next.js build pipeline to use the faster bundler without losing existing module processing logic.

Turbopack HMR slowness is diagnosed by performance profiling to identify cache misses and bundling bottlenecks. Optimizing HMR requires adjusting your top-level Turbopack settings to ensure reliable module replacement and faster reloads.

Configuring top-level Turbopack options in Next.js involves setting up modern configuration parameters to replace older experimental settings. This provides proper bundler guidance and enables faster builds and instant reloading for your project.

Turbopack can be used for production builds, requiring production diagnostics to validate the new pipeline. It helps diagnose oversized bundles and build regressions to ensure reliable modernization for large Next.js applications.

Handling CSS differences during webpack to Turbopack migration requires resolving specific CSS handling configurations. This Skill provides guidance to resolve these bundler-specific failures and update your config for the new build pipeline.

Turbopack limitations involve potential webpack parity issues where certain loader or alias patterns lack direct equivalents. You should use production diagnostics to identify build regressions and determine if specific webpack features are unsupported.