dev-turbopack

Guide Turbopack migration and diagnostics for Next.js projects.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Conradmaker/copilot-cockpit --skill dev-turbopack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-turbopack
Source: https://github.com/Conradmaker/copilot-cockpit/tree/main/.github/skills/dev-turbopack
Command: npx skills add https://github.com/Conradmaker/copilot-cockpit --skill dev-turbopack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turbopack migrations and diagnostics for Next.js projects, helping teams decide when to migrate, configure parity, and optimize development and build performance.

Core Features & Use Cases

  • Top-level Turbopack configuration guidance for Next.js projects
  • Parity-focused migration patterns from webpack to Turbopack
  • Diagnostics and tracing workflows to diagnose build and dev performance
  • Guidance on CSS/asset handling parity and build-time optimizations

Quick Start

Review your project’s turbopack settings and apply the recommended migration guidelines, then run a build to verify parity.

Frequently Asked Questions about dev-turbopack

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

FAQPage Schema
How do I migrate my Next.js project from webpack to Turbopack?

Diagnosing Turbopack build failures in Next.js uses tracing-based diagnostics workflows. These tracing workflows identify import graph issues, bundle size anomalies, and build failures across both development and production builds.

What is the best way to configure Turbopack for CSS and asset handling parity?

Configuring Turbopack for CSS and asset handling parity requires applying top-level Turbopack configuration guidance in your Next.js project. This ensures build-time optimizations match your previous webpack asset handling behavior.

Why does my Turbopack development performance lag and how can I trace it?

Diagnosing Turbopack build failures in Next.js uses tracing-based diagnostics workflows. These tracing workflows identify import graph issues, bundle size anomalies, and build failures across both development and production builds.

Can I use Turbopack with my existing Next.js webpack configuration?

Using Turbopack with existing Next.js webpack configurations requires checking top-level Turbopack settings and applying parity-focused migration patterns. You must verify CSS and asset handling parity after running a build.

Does Turbopack support tracing-based diagnostics for production builds?

Turbopack supports tracing-based diagnostics for Next.js production builds. These tracing workflows diagnose build and dev performance by identifying import graph issues, bundle size anomalies, and build failures.