import-graph

To map module dependencies in a TypeScript codebase, you can analyze direct imports and traverse transitive import trees to reveal the full dependency surface and detect circular imports. This process exposes exactly what each file pulls in and who depends on it.

The best way to see who imports a specific Python module across your project is to generate an importers tree. This reveals all files that depend on your target module, allowing you to accurately assess the impact of modifying or deleting that file.

Yes, dependency graph analysis handles type-only imports in both Python and TypeScript. It features TypeImports awareness to correctly process these statements, ensuring your dependency surface mapping avoids false positives from type-only references.

To traverse a transitive import tree starting from a single JavaScript file, you run an import tree analysis against that file. This traverses all nested dependencies from your starting module to reveal its complete dependency graph.

Yes, you can use import graph tools to plan codebase modularization for large projects. By mapping direct imports and full dependency trees, you can assess dependency surfaces and identify structural boundaries to effectively split your codebase.