You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-13Lines changed: 9 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,10 @@
1
1
# StackTower
2
2
3
-
Traditional dependency graphs are hairballs—nodes and edges sprawling in every direction. StackTower renders them as **layered towers**that reveal structure at a glance:
3
+
Inspired by [XKCD #2347](https://xkcd.com/2347/), StackTower renders dependency graphs as **physical towers** where blocks rest on what they depend on. Your application sits at the top, supported by libraries below—all the way down to that one critical package maintained by *some dude in Nebraska*.
4
4
5
-
-**Width = Importance** — Packages supporting more of your code get more visual weight
6
-
-**Depth = Foundation** — See what's at the bottom of your stack
7
-
-**No Crossings** — Optimal ordering eliminates the spaghetti
5
+
Traditional node-link diagrams are technically correct but don't *feel* like anything. Tower visualizations tap into intuition: width shows importance, depth reveals foundation, and the structure makes hidden dependencies visible at a glance.
8
6
9
-
The result: you can finally *see* your dependency structure instead of deciphering it.
10
-
11
-
📖 **[Interactive examples at stacktower.io](https://www.stacktower.io)**
7
+
📖 **[Read the full story at stacktower.io](https://www.stacktower.io)**
12
8
13
9
## Quick Start
14
10
@@ -35,13 +31,13 @@ StackTower works in two stages: **parse** dependency data from package registrie
0 commit comments