dep-graph

Finding circular imports in a TypeScript project requires analyzing the module dependency graph to detect cycles. This involves scanning import statements across your codebase to identify interdependent modules and providing actionable refactor guidance to break those cycles.

Module coupling analysis identifies high fan-in and fan-out dependencies to locate risky design cells in your codebase. You need this when adding new features or planning refactoring to ensure new dependencies do not introduce cycles and to help establish safe module boundaries.

Yes, you can analyze JavaScript dependencies across different build tools and frameworks. The analysis applies to projects with multiple interdependent modules, enabling quick discovery of problematic import graphs regardless of the specific build setup used.

To generate a dependency graph for a JavaScript codebase, run an analysis targeting an entry file like src/index.ts. This produces an actionable visualization of import relationships and reports circular imports to help plan safe module boundaries.

To locate high-coupling modules for safer refactoring, perform a coupling analysis to highlight modules with high fan-in and fan-out. This identifies risky design cells in your import graph, enabling you to plan safe module boundaries and avoid introducing cycles.