[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E24X88FC23VXDNJ58JV24X":3,"skill-same:01M6E24X88FC23VXDNJ58JV24X":105},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":76,"commitSha":77,"skillDirectory":78,"forksCount":79,"repositoryHtmlUrl":80,"repositoryHomepageUrl":81,"ownerHtmlUrl":82,"ownerBlogUrl":83,"ownerDescription":6,"updatedAt":84,"install":85,"resources":98},"01M6E24X88FC23VXDNJ58JV24X","turbopack",null,"Turbopack expert guidance. Use when configuring the Next.js bundler, optimizing HMR, debugging build issues, or understanding the Turbopack vs Webpack differences.","ByeongminLee\u002Fnextjs-claude-code","ByeongminLee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F71276006?v=4","01M6E1S467E7GC0NE144SWHC0V","Byeongmin Lee","01M6E1S4AV3W0B08Z2YBK26VG9",3,"MIT","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fturbopack\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"configure","speed","next","build","expert","guidance","up","use","fix","syntax","architecture","Next.js","nextjs","server","https","issues","dev","debugging","config","2026-11-10 10:12:30",false,"---\nname: turbopack\ndescription: Turbopack expert guidance. Use when configuring the Next.js bundler, optimizing HMR, debugging build issues, or understanding the Turbopack vs Webpack differences.\nmetadata:\n  priority: 4\n  docs:\n    - \"https:\u002F\u002Fturbo.build\u002Fpack\u002Fdocs\"\n    - \"https:\u002F\u002Fnextjs.org\u002Fdocs\u002Farchitecture\u002Fturbopack\"\n  sitemap: \"https:\u002F\u002Fturbo.build\u002Fsitemap.xml\"\n  pathPatterns: \n    - 'next.config.*'\n  bashPatterns: \n    - '\\bnext\\s+dev\\s+--turbo\\b'\n    - '\\bnext\\s+dev\\s+--turbopack\\b'\nretrieval:\n  aliases:\n    - next bundler\n    - turbopack\n    - fast bundler\n    - hmr\n  intents:\n    - enable turbopack\n    - fix build issue\n    - speed up dev server\n    - configure bundler\n  entities:\n    - Turbopack\n    - HMR\n    - bundler\n    - next dev --turbopack\nchainTo:\n  -\n    pattern: 'webpack\\s*:\\s*\\(|webpack\\s*\\(config'\n    targetSkill: nextjs\n    message: 'Webpack config detected — loading Next.js guidance for migrating webpack customizations to Turbopack top-level config in Next.js 16.'\n  -\n    pattern: 'turbopack\\s*:\\s*\\{|experimental\\.turbopack'\n    targetSkill: nextjs\n    message: 'Turbopack configuration detected — loading Next.js guidance for top-level turbopack config syntax in Next.js 16 (moved from experimental.turbopack).'\n\n---\n\n# Turbopack\n\nYou are an expert in Turbopack — the Rust-powered JavaScript\u002FTypeScript bundler built by Vercel. It is the default bundler in Next.js 16.\n\n## Key Features\n\n- **Instant HMR**: Hot Module Replacement that doesn't degrade with app size\n- **File System Caching (Stable)**: Dev server artifacts cached on disk between restarts — up to 14x faster startup on large projects. Enabled by default in Next.js 16.1+, no config needed. Build caching planned next.\n- **Multi-environment builds**: Browser, Server, Edge, SSR, React Server Components\n- **Native RSC support**: Built for React Server Components from the ground up\n- **TypeScript, JSX, CSS, CSS Modules, WebAssembly**: Out of the box\n- **Rust-powered**: Incremental computation engine for maximum performance\n\n## Configuration (Next.js 16)\n\nIn Next.js 16, Turbopack config is top-level (moved from `experimental.turbopack`):\n\n```js\n\u002F\u002F next.config.ts\nimport type { NextConfig } from 'next'\n\nconst nextConfig: NextConfig = {\n  turbopack: {\n    \u002F\u002F Resolve aliases (like webpack resolve.alias)\n    resolveAlias: {\n      'old-package': 'new-package',\n    },\n    \u002F\u002F Custom file extensions to resolve\n    resolveExtensions: ['.ts', '.tsx', '.js', '.jsx', '.json'],\n  },\n}\n\nexport default nextConfig\n```\n\n## CSS and CSS Modules Handling\n\nTurbopack handles CSS natively without additional configuration.\n\n### Global CSS\n\nImport global CSS in your root layout:\n\n```tsx\n\u002F\u002F app\u002Flayout.tsx\nimport '.\u002Fglobals.css'\n```\n\n### CSS Modules\n\nCSS Modules work out of the box with `.module.css` files:\n\n```tsx\n\u002F\u002F components\u002FButton.tsx\nimport styles from '.\u002FButton.module.css'\n\nexport function Button({ children }) {\n  return \u003Cbutton className={styles.primary}>{children}\u003C\u002Fbutton>\n}\n```\n\n### PostCSS\n\nTurbopack reads your `postcss.config.js` automatically. Tailwind CSS v4 works with zero config:\n\n```js\n\u002F\u002F postcss.config.js\nmodule.exports = {\n  plugins: {\n    '@tailwindcss\u002Fpostcss': {},\n    autoprefixer: {},\n  },\n}\n```\n\n### Sass \u002F SCSS\n\nInstall `sass` and import `.scss` files directly — Turbopack compiles them natively:\n\n```bash\nnpm install sass\n```\n\n```tsx\nimport styles from '.\u002FComponent.module.scss'\n```\n\n### Common CSS pitfalls\n\n- **CSS ordering differs from webpack**: Turbopack may load CSS chunks in a different order. Avoid relying on source-order specificity across files — use more specific selectors or CSS Modules.\n- **`@import` in global CSS**: Use standard CSS `@import` — Turbopack resolves them, but circular imports cause build failures.\n- **CSS-in-JS libraries**: `styled-components` and `emotion` work but require their SWC plugins configured under `compiler` in next.config.\n\n## Tree Shaking\n\nTurbopack performs tree shaking at the module level in production builds. Key behaviors:\n\n- **ES module exports**: Only used exports are included — write `export` on each function\u002Fconstant rather than barrel `export *`\n- **Side-effect-free packages**: Mark packages as side-effect-free in `package.json` to enable aggressive tree shaking:\n\n```json\n{\n  \"name\": \"my-ui-lib\",\n  \"sideEffects\": false\n}\n```\n\n- **Barrel file optimization**: Turbopack can skip unused re-exports from barrel files (`index.ts`) when the package declares `\"sideEffects\": false`\n- **Dynamic imports**: `import()` expressions create async chunk boundaries — Turbopack splits these into separate chunks automatically\n\n### Diagnosing large bundles\n\n**Built-in analyzer (Next.js 16.1+, experimental)**: Works natively with Turbopack. Offers route-specific filtering, import tracing, and RSC boundary analysis:\n\n```ts\n\u002F\u002F next.config.ts\nconst nextConfig: NextConfig = {\n  experimental: {\n    bundleAnalyzer: true,\n  },\n}\n```\n\n**Legacy `@next\u002Fbundle-analyzer`**: Still works as a fallback:\n\n```bash\nANALYZE=true next build\n```\n\n```ts\n\u002F\u002F next.config.ts\nimport withBundleAnalyzer from '@next\u002Fbundle-analyzer'\n\nconst nextConfig = withBundleAnalyzer({\n  enabled: process.env.ANALYZE === 'true',\n})({\n  \u002F\u002F your config\n})\n```\n\n## Custom Loader Migration from Webpack\n\nTurbopack does not support webpack loaders directly. Here is how to migrate common patterns:\n\n| Webpack Loader | Turbopack Equivalent |\n|----------------|---------------------|\n| `css-loader` + `style-loader` | Built-in CSS support — remove loaders |\n| `sass-loader` | Built-in — install `sass` package |\n| `postcss-loader` | Built-in — reads `postcss.config.js` |\n| `file-loader` \u002F `url-loader` | Built-in static asset handling |\n| `svgr` \u002F `@svgr\u002Fwebpack` | Use `@svgr\u002Fwebpack` via `turbopack.rules` |\n| `raw-loader` | Use `import x from '.\u002Ffile?raw'` |\n| `graphql-tag\u002Floader` | Use a build-time codegen step instead |\n| `worker-loader` | Use native `new Worker(new URL(...))` syntax |\n\n### Configuring custom rules (loader replacement)\n\nFor loaders that have no built-in equivalent, use `turbopack.rules`:\n\n```js\n\u002F\u002F next.config.ts\nconst nextConfig: NextConfig = {\n  turbopack: {\n    rules: {\n      '*.svg': {\n        loaders: ['@svgr\u002Fwebpack'],\n        as: '*.js',\n      },\n    },\n  },\n}\n```\n\n### When migration isn't possible\n\nIf a webpack loader has no Turbopack equivalent and no workaround, fall back to webpack:\n\n```js\nconst nextConfig: NextConfig = {\n  bundler: 'webpack',\n}\n```\n\nFile an issue at [github.com\u002Fvercel\u002Fnext.js](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fnext.js) — the Turbopack team tracks loader parity requests.\n\n## Production Build Diagnostics\n\n### Build failing with Turbopack\n\n1. **Check for unsupported config**: Remove any `webpack()` function from next.config — it's ignored by Turbopack and may mask the real config\n2. **Verify `turbopack.rules`**: Ensure custom rules reference valid loaders that are installed\n3. **Check for Node.js built-in usage in edge\u002Fclient**: Turbopack enforces environment boundaries — `fs`, `path`, etc. cannot be imported in client or edge bundles\n4. **Module not found errors**: Ensure `turbopack.resolveAlias` covers any custom resolution that was previously in webpack config\n\n### Build output too large\n\n- Audit `\"use client\"` directives — each client component boundary creates a new chunk\n- Check for accidentally bundled server-only packages in client components\n- Use `server-only` package to enforce server\u002Fclient boundaries at import time:\n\n```bash\nnpm install server-only\n```\n\n```ts\n\u002F\u002F lib\u002Fdb.ts\nimport 'server-only' \u002F\u002F Build fails if imported in a client component\n```\n\n### Comparing webpack vs Turbopack output\n\nRun both bundlers and compare:\n\n```bash\n# Turbopack build (default in Next.js 16)\nnext build\n\n# Webpack build\nBUNDLER=webpack next build\n```\n\nCompare `.next\u002F` output sizes and page-level chunks.\n\n## Performance Profiling\n\n### HMR profiling\n\nEnable verbose HMR timing in development:\n\n```bash\nNEXT_TURBOPACK_TRACING=1 next dev\n```\n\nThis writes a `trace.json` to the project root — open it in `chrome:\u002F\u002Ftracing` or [Perfetto](https:\u002F\u002Fui.perfetto.dev\u002F) to see module-level timing.\n\n### Build profiling\n\nProfile production builds:\n\n```bash\nNEXT_TURBOPACK_TRACING=1 next build\n```\n\nLook for:\n- **Long-running transforms**: Indicates a slow SWC plugin or heavy PostCSS config\n- **Large module graphs**: Reduce barrel file re-exports\n- **Cache misses**: If incremental builds aren't hitting cache, check for files that change every build (e.g., generated timestamps)\n\n### Memory usage\n\nTurbopack's Rust core manages its own memory. If builds OOM:\n- Increase Node.js heap: `NODE_OPTIONS='--max-old-space-size=8192' next build`\n- Reduce concurrent tasks if running inside Turborepo: `turbo build --concurrency=2`\n\n## Turbopack vs Webpack\n\n| Feature | Turbopack | Webpack |\n|---------|-----------|---------|\n| Language | Rust | JavaScript |\n| HMR speed | Constant (O(1)) | Degrades with app size |\n| RSC support | Native | Plugin-based |\n| Cold start | Fast | Slower |\n| Ecosystem | Growing | Massive (loaders, plugins) |\n| Status in Next.js 16 | Default | Still supported |\n| Tree shaking | Module-level | Module-level |\n| CSS handling | Built-in | Requires loaders |\n| Production builds | Supported | Supported |\n\n## When You Might Need Webpack\n\n- Custom webpack loaders with no Turbopack equivalent\n- Complex webpack plugin configurations (e.g., `ModuleFederationPlugin`)\n- Specific webpack features not yet in Turbopack (e.g., custom `externals` functions)\n\nTo use webpack instead:\n```js\n\u002F\u002F next.config.ts\nconst nextConfig: NextConfig = {\n  bundler: 'webpack', \u002F\u002F Opt out of Turbopack\n}\n```\n\n## Development vs Production\n\n- **Development**: Turbopack provides instant HMR and fast refresh\n- **Production**: Turbopack handles the production build (replaces webpack in Next.js 16)\n\n## Common Issues\n\n1. **Missing loader equivalent**: Some webpack loaders don't have Turbopack equivalents yet. Check Turbopack docs for supported transformations.\n2. **Config migration**: Move `experimental.turbopack` to top-level `turbopack` in next.config.\n3. **Custom aliases**: Use `turbopack.resolveAlias` instead of `webpack.resolve.alias`.\n4. **CSS ordering changes**: Test visual regressions when migrating — CSS chunk order may differ.\n5. **Environment boundary errors**: Server-only modules imported in client components fail at build time — use `server-only` package.\n\n## Official Documentation\n\n- [Turbopack](https:\u002F\u002Fturborepo.dev\u002Fpack)\n- [Turbopack Documentation](https:\u002F\u002Fturborepo.dev\u002Fpack\u002Fdocs)\n- [Next.js Turbopack Config](https:\u002F\u002Fnextjs.org\u002Fdocs\u002Fapp\u002Fapi-reference\u002Fconfig\u002Fnext-config-js\u002Fturbopack)\n- [GitHub: Turbopack](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fturborepo)\n","# Turbopack\n\nYou are an expert in Turbopack — the Rust-powered JavaScript\u002FTypeScript bundler built by Vercel. It is the default bundler in Next.js 16.\n\n## Key Features\n\n- **Instant HMR**: Hot Module Replacement that doesn't degrade with app size\n- **File System Caching (Stable)**: Dev server artifacts cached on disk between restarts — up to 14x faster startup on large projects. Enabled by default in Next.js 16.1+, no config needed. Build caching planned next.\n- **Multi-environment builds**: Browser, Server, Edge, SSR, React Server Components\n- **Native RSC support**: Built for React Server Components from the ground up\n- **TypeScript, JSX, CSS, CSS Modules, WebAssembly**: Out of the box\n- **Rust-powered**: Incremental computation engine for maximum performance\n\n## Configuration (Next.js 16)\n\nIn Next.js 16, Turbopack config is top-level (moved from `experimental.turbopack`):\n\n```js\n\u002F\u002F next.config.ts\nimport type { NextConfig } from 'next'\n\nconst nextConfig: NextConfig = {\n  turbopack: {\n    \u002F\u002F Resolve aliases (like webpack resolve.alias)\n    resolveAlias: {\n      'old-package': 'new-package',\n    },\n    \u002F\u002F Custom file extensions to resolve\n    resolveExtensions: ['.ts', '.tsx', '.js', '.jsx', '.json'],\n  },\n}\n\nexport default nextConfig\n```\n\n## CSS and CSS Modules Handling\n\nTurbopack handles CSS natively without additional configuration.\n\n### Global CSS\n\nImport global CSS in your root layout:\n\n```tsx\n\u002F\u002F app\u002Flayout.tsx\nimport '.\u002Fglobals.css'\n```\n\n### CSS Modules\n\nCSS Modules work out of the box with `.module.css` files:\n\n```tsx\n\u002F\u002F components\u002FButton.tsx\nimport styles from '.\u002FButton.module.css'\n\nexport function Button({ children }) {\n  return \u003Cbutton className={styles.primary}>{children}\u003C\u002Fbutton>\n}\n```\n\n### PostCSS\n\nTurbopack reads your `postcss.config.js` automatically. Tailwind CSS v4 works with zero config:\n\n```js\n\u002F\u002F postcss.config.js\nmodule.exports = {\n  plugins: {\n    '@tailwindcss\u002Fpostcss': {},\n    autoprefixer: {},\n  },\n}\n```\n\n### Sass \u002F SCSS\n\nInstall `sass` and import `.scss` files directly — Turbopack compiles them natively:\n\n```bash\nnpm install sass\n```\n\n```tsx\nimport styles from '.\u002FComponent.module.scss'\n```\n\n### Common CSS pitfalls\n\n- **CSS ordering differs from webpack**: Turbopack may load CSS chunks in a different order. Avoid relying on source-order specificity across files — use more specific selectors or CSS Modules.\n- **`@import` in global CSS**: Use standard CSS `@import` — Turbopack resolves them, but circular imports cause build failures.\n- **CSS-in-JS libraries**: `styled-components` and `emotion` work but require their SWC plugins configured under `compiler` in next.config.\n\n## Tree Shaking\n\nTurbopack performs tree shaking at the module level in production builds. Key behaviors:\n\n- **ES module exports**: Only used exports are included — write `export` on each function\u002Fconstant rather than barrel `export *`\n- **Side-effect-free packages**: Mark packages as side-effect-free in `package.json` to enable aggressive tree shaking:\n\n```json\n{\n  \"name\": \"my-ui-lib\",\n  \"sideEffects\": false\n}\n```\n\n- **Barrel file optimization**: Turbopack can skip unused re-exports from barrel files (`index.ts`) when the package declares `\"sideEffects\": false`\n- **Dynamic imports**: `import()` expressions create async chunk boundaries — Turbopack splits these into separate chunks automatically\n\n### Diagnosing large bundles\n\n**Built-in analyzer (Next.js 16.1+, experimental)**: Works natively with Turbopack. Offers route-specific filtering, import tracing, and RSC boundary analysis:\n\n```ts\n\u002F\u002F next.config.ts\nconst nextConfig: NextConfig = {\n  experimental: {\n    bundleAnalyzer: true,\n  },\n}\n```\n\n**Legacy `@next\u002Fbundle-analyzer`**: Still works as a fallback:\n\n```bash\nANALYZE=true next build\n```\n\n```ts\n\u002F\u002F next.config.ts\nimport withBundleAnalyzer from '@next\u002Fbundle-analyzer'\n\nconst nextConfig = withBundleAnalyzer({\n  enabled: process.env.ANALYZE === 'true',\n})({\n  \u002F\u002F your config\n})\n```\n\n## Custom Loader Migration from Webpack\n\nTurbopack does not support webpack loaders directly. Here is how to migrate common patterns:\n\n| Webpack Loader | Turbopack Equivalent |\n|----------------|---------------------|\n| `css-loader` + `style-loader` | Built-in CSS support — remove loaders |\n| `sass-loader` | Built-in — install `sass` package |\n| `postcss-loader` | Built-in — reads `postcss.config.js` |\n| `file-loader` \u002F `url-loader` | Built-in static asset handling |\n| `svgr` \u002F `@svgr\u002Fwebpack` | Use `@svgr\u002Fwebpack` via `turbopack.rules` |\n| `raw-loader` | Use `import x from '.\u002Ffile?raw'` |\n| `graphql-tag\u002Floader` | Use a build-time codegen step instead |\n| `worker-loader` | Use native `new Worker(new URL(...))` syntax |\n\n### Configuring custom rules (loader replacement)\n\nFor loaders that have no built-in equivalent, use `turbopack.rules`:\n\n```js\n\u002F\u002F next.config.ts\nconst nextConfig: NextConfig = {\n  turbopack: {\n    rules: {\n      '*.svg': {\n        loaders: ['@svgr\u002Fwebpack'],\n        as: '*.js',\n      },\n    },\n  },\n}\n```\n\n### When migration isn't possible\n\nIf a webpack loader has no Turbopack equivalent and no workaround, fall back to webpack:\n\n```js\nconst nextConfig: NextConfig = {\n  bundler: 'webpack',\n}\n```\n\nFile an issue at [github.com\u002Fvercel\u002Fnext.js](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fnext.js) — the Turbopack team tracks loader parity requests.\n\n## Production Build Diagnostics\n\n### Build failing with Turbopack\n\n1. **Check for unsupported config**: Remove any `webpack()` function from next.config — it's ignored by Turbopack and may mask the real config\n2. **Verify `turbopack.rules`**: Ensure custom rules reference valid loaders that are installed\n3. **Check for Node.js built-in usage in edge\u002Fclient**: Turbopack enforces environment boundaries — `fs`, `path`, etc. cannot be imported in client or edge bundles\n4. **Module not found errors**: Ensure `turbopack.resolveAlias` covers any custom resolution that was previously in webpack config\n\n### Build output too large\n\n- Audit `\"use client\"` directives — each client component boundary creates a new chunk\n- Check for accidentally bundled server-only packages in client components\n- Use `server-only` package to enforce server\u002Fclient boundaries at import time:\n\n```bash\nnpm install server-only\n```\n\n```ts\n\u002F\u002F lib\u002Fdb.ts\nimport 'server-only' \u002F\u002F Build fails if imported in a client component\n```\n\n### Comparing webpack vs Turbopack output\n\nRun both bundlers and compare:\n\n```bash\n# Turbopack build (default in Next.js 16)\nnext build\n\n# Webpack build\nBUNDLER=webpack next build\n```\n\nCompare `.next\u002F` output sizes and page-level chunks.\n\n## Performance Profiling\n\n### HMR profiling\n\nEnable verbose HMR timing in development:\n\n```bash\nNEXT_TURBOPACK_TRACING=1 next dev\n```\n\nThis writes a `trace.json` to the project root — open it in `chrome:\u002F\u002Ftracing` or [Perfetto](https:\u002F\u002Fui.perfetto.dev\u002F) to see module-level timing.\n\n### Build profiling\n\nProfile production builds:\n\n```bash\nNEXT_TURBOPACK_TRACING=1 next build\n```\n\nLook for:\n- **Long-running transforms**: Indicates a slow SWC plugin or heavy PostCSS config\n- **Large module graphs**: Reduce barrel file re-exports\n- **Cache misses**: If incremental builds aren't hitting cache, check for files that change every build (e.g., generated timestamps)\n\n### Memory usage\n\nTurbopack's Rust core manages its own memory. If builds OOM:\n- Increase Node.js heap: `NODE_OPTIONS='--max-old-space-size=8192' next build`\n- Reduce concurrent tasks if running inside Turborepo: `turbo build --concurrency=2`\n\n## Turbopack vs Webpack\n\n| Feature | Turbopack | Webpack |\n|---------|-----------|---------|\n| Language | Rust | JavaScript |\n| HMR speed | Constant (O(1)) | Degrades with app size |\n| RSC support | Native | Plugin-based |\n| Cold start | Fast | Slower |\n| Ecosystem | Growing | Massive (loaders, plugins) |\n| Status in Next.js 16 | Default | Still supported |\n| Tree shaking | Module-level | Module-level |\n| CSS handling | Built-in | Requires loaders |\n| Production builds | Supported | Supported |\n\n## When You Might Need Webpack\n\n- Custom webpack loaders with no Turbopack equivalent\n- Complex webpack plugin configurations (e.g., `ModuleFederationPlugin`)\n- Specific webpack features not yet in Turbopack (e.g., custom `externals` functions)\n\nTo use webpack instead:\n```js\n\u002F\u002F next.config.ts\nconst nextConfig: NextConfig = {\n  bundler: 'webpack', \u002F\u002F Opt out of Turbopack\n}\n```\n\n## Development vs Production\n\n- **Development**: Turbopack provides instant HMR and fast refresh\n- **Production**: Turbopack handles the production build (replaces webpack in Next.js 16)\n\n## Common Issues\n\n1. **Missing loader equivalent**: Some webpack loaders don't have Turbopack equivalents yet. Check Turbopack docs for supported transformations.\n2. **Config migration**: Move `experimental.turbopack` to top-level `turbopack` in next.config.\n3. **Custom aliases**: Use `turbopack.resolveAlias` instead of `webpack.resolve.alias`.\n4. **CSS ordering changes**: Test visual regressions when migrating — CSS chunk order may differ.\n5. **Environment boundary errors**: Server-only modules imported in client components fail at build time — use `server-only` package.\n\n## Official Documentation\n\n- [Turbopack](https:\u002F\u002Fturborepo.dev\u002Fpack)\n- [Turbopack Documentation](https:\u002F\u002Fturborepo.dev\u002Fpack\u002Fdocs)\n- [Next.js Turbopack Config](https:\u002F\u002Fnextjs.org\u002Fdocs\u002Fapp\u002Fapi-reference\u002Fconfig\u002Fnext-config-js\u002Fturbopack)\n- [GitHub: Turbopack](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fturborepo)\n",{"name":5,"chainTo":43,"metadata":50,"retrieval":61,"description":7},[44,47],{"message":45,"pattern":46,"targetSkill":31},"Webpack config detected — loading Next.js guidance for migrating webpack customizations to Turbopack top-level config in Next.js 16.","webpack\\s*:\\s*\\(|webpack\\s*\\(config",{"message":48,"pattern":49,"targetSkill":31},"Turbopack configuration detected — loading Next.js guidance for top-level turbopack config syntax in Next.js 16 (moved from experimental.turbopack).","turbopack\\s*:\\s*\\{|experimental\\.turbopack",{"docs":51,"sitemap":54,"priority":55,"bashPatterns":56,"pathPatterns":59},[52,53],"https:\u002F\u002Fturbo.build\u002Fpack\u002Fdocs","https:\u002F\u002Fnextjs.org\u002Fdocs\u002Farchitecture\u002Fturbopack","https:\u002F\u002Fturbo.build\u002Fsitemap.xml",4,[57,58],"\\bnext\\s+dev\\s+--turbo\\b","\\bnext\\s+dev\\s+--turbopack\\b",[60],"next.config.*",{"aliases":62,"intents":66,"entities":71},[63,5,64,65],"next bundler","fast bundler","hmr",[67,68,69,70],"enable turbopack","fix build issue","speed up dev server","configure bundler",[72,73,74,75],"Turbopack","HMR","bundler","next dev --turbopack","main","330a71e3d12264515ce3477e446d29fd34a88a9d","template\u002Fskills-archive\u002Fturbopack",1,"https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code","https:\u002F\u002Fbyeongminlee.github.io\u002Fnextjs-claude-code\u002F","https:\u002F\u002Fgithub.com\u002FByeongminLee","byeongmin.dev","2026-03-27 12:45:44",{"source":8,"skillName":5,"commands":86,"prompt":96,"zipAvailable":97},[87,90,93],{"tool":88,"command":89},"npx","npx skills add ByeongminLee\u002Fnextjs-claude-code --skill turbopack",{"tool":91,"command":92},"bunx","bunx skills add ByeongminLee\u002Fnextjs-claude-code --skill turbopack",{"tool":94,"command":95},"pnpm","pnpm dlx skills add ByeongminLee\u002Fnextjs-claude-code --skill turbopack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fturbopack\u002FSKILL.md",true,[99],{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"_AIWF_IMPORT.json","REFERENCE","参考文档",372,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fbash-defensive-patterns\u002F_AIWF_IMPORT.json",[106,124,132,160,188,226],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":38},"01M6E263DRDCZ5AX01N6MDYC6Z","zustand","Zustand state management guide. Use when working with store code (src\u002Fstore\u002F**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fzustand\u002FSKILL.md",[],[108,113,114,115,116,26,117,118,119,120,121,122,123],"triggers","state management","zustand state","implementation","guide","management","src","actions","state","code","development",{"skillNo":125,"name":126,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":38},"01M6E260QFP3ZMXY2Y6KTGZYXS","web-vitals","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fweb-vitals\u002FSKILL.md",[],[130,131],"web vitals","web",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":143,"publishedAt":38},"01M6E25QEKXHH092S5RB0GKM0K","vercel-storage","Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fvercel-storage\u002FSKILL.md",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[144,145,146,147,148,149,150,31,151,152,153,154,155,156,157,158,23,25,159,19],"vercel","vercel storage","storage","supabase","api","mongodb","SET","database","auth","migrate","click","app","neon","prisma","postgres","auto",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":172,"publishedAt":38},"01M6E25EC9YM4QM0KBQ2W5R1SC","vercel-functions","Vercel Functions expert guidance — Serverless Functions, Edge Functions, Fluid Compute, streaming, Cron Jobs, and runtime configuration. Use when configuring, debugging, or optimizing server-side code running on Vercel.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fvercel-functions\u002FSKILL.md",[166,167],{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},{"categoryNo":168,"categoryName":169,"taxonomyType":170,"taxonomyTypeDesc":171},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[173,144,174,175,176,177,178,179,155,156,180,181,182,183,32,184,185,186,187,23],"functions","vercel functions","local","shared","project","time","apps","express","vercel ai sdk","router","loop","logs","streaming","delete","create",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":209,"publishedAt":38},"01M6E25873YRYP96MSQK7E2D9X","ui-ux-pro-max","UI\u002FUX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui, and HTML\u002FCSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn\u002Fui MCP for component search and examples.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fui-ux-pro-max\u002FSKILL.md",[194,197,200,203,206],{"categoryNo":195,"categoryName":196,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":198,"categoryName":199,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":201,"categoryName":202,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":204,"categoryName":205,"taxonomyType":170,"taxonomyTypeDesc":171},"01JBSEEDCAT000000000000032","设计师",{"categoryNo":207,"categoryName":208,"taxonomyType":170,"taxonomyTypeDesc":171},"01JBSEEDCAT000000000000033","数据分析师",[210,211,212,213,214,215,216,217,155,218,219,27,220,221,222,223,224,120,225,187],"ui ux pro max","ui","ux","max","css","MCP","design","react","card","chart","projects","plan","improve","Tailwind","Animation","search",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":232,"publishedAt":38},"01M6E251G3FJSRB9019V20QK9X","turborepo","Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines,\ndependsOn, caching, remote cache, the \"turbo\" CLI, --filter, --affected, CI optimization, environment\nvariables, internal packages, monorepo structure\u002Fbest practices, and boundaries.\n\nUse when user: configures tasks\u002Fworkflows\u002Fpipelines, creates packages, sets up\nmonorepo, shares code between apps, runs changed\u002Faffected packages, debugs cache,\nor has apps\u002Fpackages directories.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fturborepo\u002FSKILL.md",[],[228,233,26,234,235,179,113,236,237,25,238,239,240,241,242,243,122,244,245,246],"cli","filter","environment variables","caching","structure","environment","monorepo","system","canary","Optimization","ci","packages","tasks","workflows"]