skills.rest
villa1
villa1COMMUNITY
Explore all skills by this author →
WebsiteGitHub

runtime-debug

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

Updated Apr 7, 2026
Search Tags:#next.js#debug#traces#module-resolution#ci-debugging#runtime-bundle#webpack-stats
One-click install
npx skills add https://github.com/villa1/backupshop --skill runtime-debug-villa1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: runtime-debug
Source: https://github.com/villa1/backupshop/tree/main/.agents/skills/runtime-debug
Command: npx skills add https://github.com/villa1/backupshop --skill runtime-debug-villa1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug and verification workflow for runtime-bundle and module-resolution regressions. Use when diagnosing unexpected module inclusions, bundle size regressions, or CI failures related to NEXT_SKIP_ISOLATE, nft.json traces, or runtime bundle selection (module.compiled.js). Covers CI env mirroring, full stack traces via __NEXT_SHOW_IGNORE_LISTED, route trace inspection, and webpack stats diffing.

Core Features & Use Cases

  • Validates runtime bundle selections and module-resolution paths across environments.
  • Traces and surfaces ignore-listed frames for debugging, and diffs webpack stats to identify regressions.
  • Use cases include CI failure diagnosis, bundle-size regressions, and environment mirroring for reproducible debugging.

Quick Start

Reproduce a regression locally by mirroring CI variables and running the provided debug workflow.

Frequently Asked Questions about runtime-debug

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

FAQPage Schema
How do I debug unexpected module inclusions in a Next.js runtime bundle?▼

Debug unexpected module inclusions in a Next.js runtime bundle by mirroring CI environment variables locally, enabling full stack traces with __NEXT_SHOW_IGNORE_LISTED, and diffing webpack stats to identify the regression source.

How do I reproduce a Next.js bundle size regression locally that only appears in CI?▼

Reproduce a Next.js bundle size regression locally by mirroring your CI environment variables and running a debug workflow that diffs webpack stats to identify the exact module-resolution changes causing the size increase.

What does NEXT_SKIP_ISOLATE do and how do I trace its behavior in Next.js builds?▼

NEXT_SKIP_ISOLATE impacts runtime bundle selection in Next.js builds, and you trace its behavior by inspecting nft.json traces and route trace outputs to diagnose module-resolution regressions across environments.

Can I use webpack stats diffing to diagnose CI runtime bundle failures?▼

Yes, you can use webpack stats diffing to diagnose CI runtime bundle failures by comparing build outputs, inspecting route traces, and surfacing ignore-listed frames to identify module-resolution regressions.

How do I surface ignore-listed stack frames when debugging Next.js module resolution?▼

Surface ignore-listed stack frames when debugging Next.js module resolution by enabling the __NEXT_SHOW_IGNORE_LISTED environment variable to expose full stack traces for accurate runtime bundle diagnosis.

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
sigitpoerwosigitpoerwo

runtime-debug

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

Community
Advanced
JuanDiego30JuanDiego30

runtime-debug

Diagnoses Cybertruck production delays and quality issues.

Community
Advanced
AgentientAgentient
2

frontend-bundle-analysis-and-optimization

Analyze and optimize JavaScript bundle size in Next.js projects.

Official
Advanced