May I suggest the following feature.
Current Situation
Dependencies between source files of a project are depicted nicely. This in particular allows to see how self contained the files in a directory are, like
- "I have only incoming links (good)."
- "Uhhh, the directory depends on its parent and two neighbors, need to work on the structure."
What I cannot see: "Hmm, this file depends on that trivial external module just to clip a string in half. Can I get rid of it?"
We cannot see if the files have external dependencies, which may create a false impression of self-containedness.
New Feature
- Optionally add one node for every file/module directly imported from external sources.
- Make it visually clear that the dependency is external. Ideas: add "external" to the graph-node's text, use elliptic node shape.
Explicit non-feature: do not show indirect external dependencies.
Example: consider a file app.ts starting with
import { create } from 'tar.js';
import { yada } from ./myyada.js"
Currently we get a dependency link app.ts -> myyada.ts. It would be nice to optionally add a link to tar.js or tar.ts.
May I suggest the following feature.
Current Situation
Dependencies between source files of a project are depicted nicely. This in particular allows to see how self contained the files in a directory are, like
What I cannot see: "Hmm, this file depends on that trivial external module just to clip a string in half. Can I get rid of it?"
We cannot see if the files have external dependencies, which may create a false impression of self-containedness.
New Feature
Explicit non-feature: do not show indirect external dependencies.
Example: consider a file
app.tsstarting withCurrently we get a dependency link
app.ts -> myyada.ts. It would be nice to optionally add a link totar.jsortar.ts.