VS Code Call Hierarchies Across Library Boundaries in a Monorepo

Viewed 14

In the context of a TS monorepo, VS Code appears unable to track call hierarchies across libraries. I haven't been able to find a solution in repos based on yarn workspaces nor Nx.

I'm currently working with a micro frontend architecture; because components tend to straddle multiple libs, a typical call hierarchy trace gets maybe one component up, if that.

I have no issues with any of the standard cross-lib IDE features - auto import / code completion / inspection / yadda.

Is there a configuration setting I'm missing, or is cross-lib call hierarchies just beyond what's supported?

0 Answers
Related