src/apiA module — one directory, with the symbols and files in it
src/db
The bar along the bottom is how much leans on it — files elsewhere that reference
straight into it, against the most depended-on box here. The count is on the box
Depends on — the box above calls, imports, extends or names a type from the box below.
Thicker is more references{declaredBasis
? ''
: '; here the layering had too few imports to trust, so it used raw counts'}
Points back up — the lighter half of a mutual dependency, or a link with no import or
declared type behind it. Drawn only while a module it touches is selected
top / bottom
A module sits one layer above everything it depends on, so entry points end up at the top
and the foundations — which depend on nothing below — at the bottom
src/apiSelected: click a module to bring out its links and list its files; everything more than one hop away fades
nothing depends on thisNo link in the index arrives here — a script, a workflow, an unreferenced corner
__tests__More than half its files are tests; off unless you turn tests on
genEvery file in it is tool-generated — nobody wrote it and nobody edits it
{#if thinCount > 0}
{thinCount} hidden
Links carrying fewer than {minWeight} references wait until you select a module they
touch, so a weak coincidence never draws as a dependency