runtime-debug
Runtime Debug
Use this skill when reproducing runtime-bundle, module-resolution, or user-bundle inclusion regressions.
Local Repro Discipline
- Mirror CI env vars when reproducing CI failures.
- Key variables:
IS_WEBPACK_TEST=1forces webpack (turbopack is default),NEXT_SKIP_ISOLATE=1skips packing next.js. - For module-resolution validation, always rerun without
NEXT_SKIP_ISOLATE=1.
Stack Trace Visibility
Set __NEXT_SHOW_IGNORE_LISTED=true to disable the ignore-list filtering in dev server error output. By default, Next.js collapses internal frames to at ignore-listed frames, which hides useful context when debugging framework internals. Defined in packages/next/src/server/patch-error-inspect.ts.
User-Bundle Regression Guardrail
When user next build starts bundling internal Node-only helpers unexpectedly:
- Inspect route trace artifacts (
.next/server/.../page.js.nft.json).
More from vercel/next.js
update-docs
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
2.4Kauthoring-skills
>
982react-vendoring
>
909flags
>
867dce-edge
>
810pr-status-triage
>
806