refactor-parallel

To refactor monorepo modules in parallel safely, build a dependency graph from tsconfig and package.json, group modules into tiered levels, and execute workers per tier sequentially to ensure downstream modules update safely after core modules.

Tiered parallel execution groups monorepo modules into dependency levels, spawns parallel workers for each module within a tier, and only moves to the next tier after all preceding modules pass their tests and type-checks successfully.

Dependency-aware monorepo refactoring applies code changes across interdependent modules while respecting their hierarchy. It is needed when applying large-scale updates like naming conventions to prevent build failures from mismatched downstream dependencies.

Yes, dependency-aware parallel refactoring supports TypeScript projects by scanning tsconfig.json and package.json files within packages and src directories to automatically map and group inter-module dependencies into execution tiers.

The best way to apply naming conventions across a monorepo is to run baseline tests, execute changes in dependency tiers starting with core modules, and finish with full monorepo test and type-check verification to catch any failures.

During parallel monorepo refactoring, if a module fails its tests or type-checks, the process stops progressing to downstream tiers and generates a final verification report listing all changed, skipped, and failed modules.