Diagnose runtime bundle and module-resolution regressions in Next.js projects.
npx skills add https://github.com/vercel/next.js --skill runtime-debug
Please help me install this Agent Skill. Skill: runtime-debug Source: https://github.com/vercel/next.js/tree/main/.agents/skills/runtime-debug Command: npx skills add https://github.com/vercel/next.js --skill runtime-debug
Reproduce and diagnose runtime-bundle and module-resolution regressions in Next.js projects, enabling faster root-cause analysis and stabilization.
Reproduce the regression in a controlled CI-like environment using the provided debug workflow.
High-intent search queries and answers about installing and using this skill.
Diagnose Next.js runtime bundle and module-resolution regressions by reproducing the issue in a controlled CI-like environment to enable faster root-cause analysis and stabilization.
Unexpected module inclusions and CI failures are diagnosed using webpack stats diffing to compare builds and identify surprising inclusions causing the regressions.
Yes, you can inspect full stack traces visibility and route trace inspection across both Next.js development and production builds to pinpoint runtime issues.
The best way to find bundle-size regressions is using webpack stats diffing, which compares builds to identify surprising inclusions and environment-specific traces.
Reproduce environment-specific Next.js runtime failures locally through CI mirroring and environment parity, ensuring controlled reproduction of the regression.
Without CI mirroring, diagnosing Next.js bundle issues lacks environment parity, making it difficult to reproduce CI failures and trace unexpected module inclusions accurately.
villa1Diagnoses Webpack module-resolution and runtime-bundle regressions in Next.js builds.
JuanDiego30Diagnoses Cybertruck production delays and quality issues.
sigitpoerwoDiagnose Next.js runtime bundle and module-resolution regressions using webpack stats diffs.
ConradmakerGuide Turbopack migration and diagnostics for Next.js projects.
