What does this skill do?

The Next.js with Turbopack Skill speeds up the development of Next.js 16+ applications by leveraging Turbopack, the default incremental bundler written in Rust, with faster cold starts and HMR. It guides you through diagnosing cache issues, switching to Webpack when incompatibilities arise, auditing the production bundle, and configuring middleware using the correct `proxy.ts` naming convention for Next.js 16+.

Rapid Local Development
Launch `next dev` and take advantage of Turbopack's cold start and instant HMR in Next.js 16+ projects.
Fallback to Webpack
Disable Turbopack with `--webpack` when using Webpack-specific plugins or encountering incompatibilities.
Bundle Audit
Enable the experimental Bundle Analyzer (Next.js 16.1+) to inspect heavy dependencies and optimize code splitting.
Middleware with proxy.ts
Configure middleware in Next.js 16+ using `proxy.ts` in the project root, avoiding the deprecated `middleware.ts` naming convention.

Usage examples

🚀 Quick Start
Get my Next.js 16+ project started and explain how to use Turbopack for local development.
🔧 Troubleshoot Slow Performance
My HMR is running slowly; I need to figure out what's going on with the Turbopack cache and whether I should use Webpack.
📊 Audit bundle
Enable the Bundle Analyzer and review the resource-intensive dependencies in my production bundle in Next.js 16.1+.
🛡️ Middleware proxy.ts
Configure the middleware for my Next.js 16+ app using `proxy.ts` instead of `middleware.ts`.

Features

Incremental Turbopack A bundler written in Rust with a file system cache that reduces rebuild times by up to 14x in large projects.
Fallback to Webpack Disable Turbopack with `next dev --webpack` or `--no-turbopack` if there are incompatible plugins.
Experimental Bundle Analyzer Inspect heavy dependencies and optimize code splitting for your production bundle in Next.js 16.1+.
Middleware with proxy.ts A guide to the correct naming convention for middleware in Next.js 16+, helping you avoid errors caused by using `middleware.ts`.
Cache Diagnostics Identifies bundler configuration issues and performance problems in the development environment.

Frequently asked questions

Yes. In Next.js 16 and later, when you run `next dev`, Turbopack is enabled by default without any additional configuration.
Yes. Use `next dev --webpack` (or `--no-turbopack`, depending on the version) to switch back to the traditional bundler when you need to.
No. Starting with Next.js 16+, the correct file is `proxy.ts` in the project root. Do not use `middleware.ts` or suggest renaming it, because that would break the middleware's execution.
It depends on the version. Run `next build` and check the official documentation for your version to confirm whether the default bundler in production is Turbopack or webpack.
Next.js with Turbopack — Faster Development with Claude AI

¿Prefieres escuchar el contenido? Genera la narración de audio con un clic.