supabase/cli · packages/stack/src
The packages/stack/src module of supabase/cli — the files it contains, which are most load-bearing, and how it couples to the rest of the codebase. Derived from the import graph.
21
Files
106
Total in-degree
9
Modules imported
7
Importing modules
A file in this module participates in a circular import — see the architecture overview.
Files in this module
Ranked by in-degree — how many other files import each one. The top of the list is where the module's weight sits.
- StackNamespace.ts15 in · 6 out · radius 41
- Service.ts13 in · 2 out · radius 58
- Artifacts.ts12 in · 3 out · radius 50
- Rpc.ts9 in · 10 out · radius 13
- FailureKind.ts9 in · 0 out · radius 61
- Commands.ts7 in · 1 out · radius 16
- Defaults.ts7 in · 0 out · radius 46
- Orchestrator.ts6 in · 3 out · radius 42
- Ports.ts5 in · 4 out · radius 41
- Proxy.ts4 in · 1 out · radius 18
- effect.ts3 in · 19 out · radius 3
- HostProcess.ts3 in · 7 out · radius 8
- Owner.ts2 in · 20 out · radius 8
- Network.ts2 in · 6 out · radius 12
- PromiseClient.ts2 in · 5 out · radius 2
- Sweep.ts2 in · 5 out · radius 7
- HttpProxy.ts2 in · 3 out · radius 17
- Lifecycle.ts2 in · 0 out · radius 59
- StackHost.ts1 in · 9 out · radius 2
- testing.ts0 in · 6 out · radius 0
- index.ts0 in · 4 out · radius 0
Depends on
Modules this one imports from (with the number of import edges).
Depended on by
Modules that import from this one — its blast radius if you change it.
Ask about supabase/cli
Explore the source with a question. Answers are AI-written, with code references.
Write your own question →Module boundaries are inferred from source directories and the import graph at the time of analysis; they can be incomplete or stale.