skills.rest
sigitpoerwo
sigitpoerwoCOMMUNITY
Explore all skills by this author →
GitHub

runtime-debug

Diagnose Next.js runtime bundle and module-resolution regressions using webpack stats diffs.

Updated Mar 29, 2026
Search Tags:#debug#runtime#nextjs#webpack#ci#bundle#module-resolution
One-click install
npx skills add https://github.com/sigitpoerwo/repoworkspace_zahra --skill runtime-debug-sigitpoerwo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: runtime-debug
Source: https://github.com/sigitpoerwo/repoworkspace_zahra/tree/main/skills/03-BELUM-DICOBA/dari-clawhub/runtime-debug
Command: npx skills add https://github.com/sigitpoerwo/repoworkspace_zahra --skill runtime-debug-sigitpoerwo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose runtime bundle and module resolution regressions that cause CI failures or unexpected user-bundle inclusions in Next.js projects.

Core Features & Use Cases

  • Mirror CI environment variables to reproduce failures consistently.
  • Inspect stack traces, nft.json traces, and route-level artifacts to identify forbidden internals and misbundled code.
  • Validate bundle composition and differences using webpack stats diffs for reliable debugging.

Quick Start

Run the runtime-debug skill in your CI or local environment to reproduce a failure and inspect route traces and bundle diffs.

Frequently Asked Questions about runtime-debug

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

FAQPage Schema
How do I debug Next.js runtime bundle and module resolution regressions?▼

To debug Next.js runtime bundle and module resolution regressions, inspect stack traces, nft.json traces, and route-level artifacts to identify forbidden internals and misbundled code causing failures.

Why does my Next.js build fail in CI but pass locally?▼

Next.js build failures in CI can happen due to environment inconsistencies. Mirror CI environment variables locally to reproduce the failure consistently and inspect route traces to find the mismatch.

How do I validate bundle composition differences using webpack stats?▼

Validate bundle composition differences by generating and comparing webpack stats diffs. This reveals misbundled code and route-level inconsistencies to ensure reliable debugging of build outputs.

What causes unexpected user-bundle inclusions in Next.js projects?▼

Unexpected user-bundle inclusions in Next.js projects are caused by module resolution regressions. Inspect nft.json traces and route-level bundle selection to identify forbidden internals bundled into the output.

Does runtime-debug work with NEXT_SKIP_ISOLATE and nft.json traces?▼

Yes, it works with NEXT_SKIP_ISOLATE and nft.json traces. It uses these route-level artifacts to reveal bundle selection inconsistencies and diagnose module resolution regressions in Next.js pipelines.

Related Skills

Explore More Software Engineering Skills→
vercelvercel
141.7k

runtime-debug

Diagnose runtime bundle and module-resolution regressions in Next.js projects.

Official
Advanced
villa1villa1

runtime-debug

Diagnoses Webpack module-resolution and runtime-bundle regressions in Next.js builds.

Community
Advanced
JuanDiego30JuanDiego30

runtime-debug

Diagnoses Cybertruck production delays and quality issues.

Community
Advanced
ksciuskscius
2

tailing-build-output

Monitor live webpack, turbo, and docker build outputs for errors and warnings.

Community
Intermediate