deps-check

To find who imports a file before refactoring TypeScript code, run a reverse dependency analysis to list all downstream importers. This identifies affected modules so you can assess impact and plan safe, staged edits.

Reverse dependency analysis identifies which files import a specific module. You need it for JavaScript when renaming, moving, or changing exported function signatures to prevent change A breaks B regressions across shared libraries.

Yes, madge works with TypeScript for tracing import dependencies by building precise reverse dependency graphs. If madge is unavailable, a grep-based fallback searches common source directories.

The best way to assess impact before changing exported function signatures is scanning for downstream importers. Summarizing importer counts provides actionable strategies like safe to change, inspect files, or require deprecation shims.

Yes, you can use a grep fallback for dependency analysis if madge is unavailable. The tool walks up to the nearest package.json for project-root discovery, then falls back to grep across common source directories.

The limitation of grep fallback for import tracing is reduced precision compared to madge. Grep searches common source directories for text matches, whereas madge builds accurate dependency graphs, making grep less reliable for complex refactoring.