impact-analysis

To map the blast radius of code changes, trace direct and indirect dependencies starting from a target file or symbol. This static analysis identifies affected modules and tests up to two dependency levels deep.

Static dependency tracing locates files that import or reference a target module. By resolving these references up to two levels deep, it maps the ripple effects and highlights test files needed to validate the changes.

You can find modules importing a shared utility or public API by running static analysis on the target file path or symbol name. The tool enumerates direct importers and resolves indirect dependencies to gauge the full impact.

Static impact analysis ignores dynamic imports and external packages, focusing exclusively on internal project references. It excludes node_modules and flags these potential gaps to ensure safe and predictable analysis.

The best way to trace code dependencies for a specific symbol is using static reference analysis. Provide the symbol name to enumerate direct and indirect importers, mapping the blast radius up to two dependency levels.

You can use static analysis to map code dependencies for large projects by tracing imports from a target file. It resolves up to two dependency levels, though dynamic imports and external packages are ignored to maintain accuracy.