Nextjs turbopack

Skill onfire7777/universal-ai-skills-library/skills/nextjs-turbopack

Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.From its SKILL.md

Install

npx -y skills add onfire7777/universal-ai-skills-library --skill nextjs-turbopack

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 472 tokens by cl100k_base, as published. Nobody here has run it

Next.js and Turbopack

Next.js 16+ uses Turbopack by default for local development: an incremental bundler written in Rust that significantly speeds up dev startup and hot updates.

When to Use

Turbopack (default dev): Use for day-to-day development. Faster cold start and HMR, especially in large apps.
Webpack (legacy dev): Use only if you hit a Turbopack bug or rely on a webpack-only plugin in dev. Disable with --webpack (or --no-turbopack depending on your Next.js version; check the docs for your release).
Production: Production build behavior (next build) may use Turbopack or webpack depending on Next.js version; check the official Next.js docs for your version.

Use when: developing or debugging Next.js 16+ apps, diagnosing slow dev startup or HMR, or optimizing production bundles.

How It Works

Turbopack: Incremental bundler for Next.js dev. Uses file-system caching so restarts are much faster (e.g. 5–14x on large projects).
Default in dev: From Next.js 16, next dev runs with Turbopack unless disabled.
File-system caching: Restarts reuse previous work; cache is typically under .next; no extra config needed for basic use.
Bundle Analyzer (Next.js 16.1+): Experimental Bundle Analyzer to inspect output and find heavy dependencies; enable via config or experimental flag (see Next.js docs for your version).

Examples

Commands

next dev
next build
next start

Usage

Run next dev for local development with Turbopack. Use the Bundle Analyzer (see Next.js docs) to optimize code-splitting and trim large dependencies. Prefer App Router and server components where possible.

Best Practices

Stay on a recent Next.js 16.x for stable Turbopack and caching behavior.
If dev is slow, ensure you're on Turbopack (default) and that the cache isn't being cleared unnecessarily.
For production bundle size issues, use the official Next.js bundle analysis tooling for your version.

What ships with it: 1 file

268 B alongside SKILL.md

agents/

openai.yaml268 B

Gives 9 of the 12 instructions most caching build skills give in 472 tokens

Counted across 103 of the 134 authors here whose files we hold, read 2026-09-06

Prefer App Router and server componentshere, and in 12 of 103, across 7 files
Stay on a recent Next.js 16.x releasehere, and in 12 of 103, across 7 files
Use the Bundle Analyzer to trim large dependencieshere, and in 12 of 103, across 7 files
Use Turbopack for day-to-day developmenthere, and in 11 of 103, across 6 files
Fall back to webpack only for Turbopack bugs or webpack-only pluginshere, and in 11 of 103, across 6 files
Set a TTL on every cache entryin 10 of 103, across 9 files
Check the official docs for your Next.js versionhere, and in 9 of 103, across 5 files
Ensure the cache is not cleared unnecessarilyhere, and in 8 of 103, across 4 files
Verify Turbopack is active when dev is slowhere, and in 8 of 103, across 4 files
Run next dev for local developmentin 7 of 103, across 6 files
Run next dev for local development with Turbopackhere, and in 6 of 103, across 2 files
Append static extensions to dynamic URLs to trigger cachingin 6 of 103, across 3 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.