Graphtia documentation · feature
Dependencies
Understand the code a selected entity relies on.
Follow what this module needs
Dependencies follow outgoing structural relationships from the selected source. They help you identify the contracts and implementations that the module relies on. Use this direction when trying to explain an implementation or prepare to isolate part of it.
checkout-service.ts imports the payment, order and validation modules. Dependents traverses the same relationship in the reverse direction.
// checkout-service.ts
import { authorizePayment } from './payment-gateway';
import { validateOrder } from './validation';Inspect a dependency in Explorer
Select checkout-service.ts from search or the project tree.
Use “Show dependencies” from the available actions.
Open payment-gateway.ts and inspect the source relationship and interface.
Repeat for validation.ts only if validation is relevant to the question. Keep unrelated imports out of the explanation.
The native query for checkout-service.ts exposes three imported modules: payment-gateway.ts, order-service.ts and validation.ts. Compare those module relationships with the import statements above. A type or function query may produce a different, narrower set.
Interpret the result at the right level
A file-level dependency says that one module relies on another. It is not the same as a direct call between two functions. A type-only relationship can constrain a change without causing runtime work. Use callers or callees when the question specifically concerns an invocation.