debug-helper

Debugging cross-stack build failures involves inspecting the build pipeline, isolating the failing project or step, and identifying TypeScript compilation errors across Angular, NestJS, and Nx environments to pinpoint root causes.

Tracing a top-level command failure to a specific package requires a structured workflow that isolates the failing step and analyzes the dependency graph within the Nx monorepo to locate the exact file and root cause.

Resolving dependency conflicts involves analyzing the dependency graph, verifying package versions, detecting duplicates, and resolving conflicts across the Angular and NestJS stack to ensure stable builds.

Nx cache issues cause non-reproducible build failures when cached outputs are corrupted or stale. Clearing or bypassing the Nx cache validates reproducibility and speeds up the debugging process.

Yes, the workflow supports running targeted tests with verbose output in NestJS to reproduce failures and locate flaky tests, ensuring failures are documented and reproducible across the stack.

Verifying module imports, DI tokens, and provider configuration in Angular is required to identify integration points and apply targeted cross-stack fixes across the monorepo environment.