nextjs-turbopack

Diagnose and optimize Next.js 16+ development with Turbopack incremental bundling and FS caching.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/inuishan/PET --skill nextjs-turbopack-inuishan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nextjs-turbopack
Source: https://github.com/inuishan/PET/tree/main/.codex/skills/nextjs-turbopack
Command: npx skills add https://github.com/inuishan/PET --skill nextjs-turbopack-inuishan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Slow dev server startup, sluggish hot module replacement, and confusion about when to use Turbopack versus webpack make Next.js development frustrating. This Skill provides clear guidance on Next.js 16+ bundler behavior so you can pick the right tool and fix dev-speed issues. ## Core Features & Use Cases - Bundler Selection Guidance: Explains when to use Turbopack (default dev bundler) versus webpack (legacy fallback via --webpack or --no-turbopack). - Dev Speed Optimization: Covers file-system caching under .next that makes restarts 5–14x faster on large projects, with no extra config needed. - Bundle Analysis: Describes the experimental Bundle Analyzer in Next.js 16.1+ for inspecting output and trimming heavy dependencies. - Use Case: Your Next.js app's dev server takes minutes to start. Use this Skill to confirm Turbopack is enabled, verify the cache isn't being cleared, and analyze the production bundle for oversized dependencies. ## Quick Start Ask the agent to diagnose why your Next.js dev server startup is slow and whether Turbopack is configured correctly.

Frequently Asked Questions about nextjs-turbopack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I speed up Next.js dev server startup?▼

Next.js 16+ uses Turbopack by default for `next dev`, which provides faster cold starts and HMR through incremental bundling and file-system caching. Ensure you are on a recent Next.js 16.x release and that the `.next` cache is not being cleared unnecessarily.

Turbopack vs webpack: which should I use for Next.js development?▼

Use Turbopack for day-to-day development since it is the default in Next.js 16+ and significantly faster. Switch to webpack only if you hit a Turbopack bug or depend on a webpack-only plugin, using the `--webpack` or `--no-turbopack` flag depending on your version.

Does Next.js 16 use Turbopack for production builds?▼

Production build behavior with `next build` may use Turbopack or webpack depending on your Next.js version. Check the official Next.js documentation for your specific release to confirm which bundler runs in production.

How do I analyze my Next.js bundle size?▼

Next.js 16.1+ includes an experimental Bundle Analyzer to inspect output and find heavy dependencies. Enable it via config or an experimental flag as described in the Next.js docs, then use the results to improve code-splitting and trim large dependencies.

Why is my Next.js dev server still slow with Turbopack?▼

Slowness usually means the file-system cache under `.next` is being cleared between restarts or you are on an older Next.js version. Stay on a recent Next.js 16.x release for stable Turbopack caching behavior, which can make restarts 5–14x faster on large projects.