uc-apx deps
Show what a component depends on (upstream) and what depends on it (downstream), traversing @-references transitively. Use —depth to limit traversal. When an ID is ambiguous, use —kind to target a specific component type.
uc-apx deps <id> [flags]| Flag | Type | Default | Description |
|---|---|---|---|
--depth | int | Maximum traversal depth (0 = unlimited) | |
--kind | string | Filter the lookup to nodes of this kind (e.g. region, breadcrumb, lov, page) |
Global Flags
Section titled “Global Flags”| Flag | Type | Default | Description |
|---|---|---|---|
--app-dir | string | . | Path to the APEX application directory |
--json-pretty | Output in pretty-printed JSON (human-readable) instead of minified JSON | ||
--toon | Output in TOON format (human-readable, token-efficient) instead of JSON |
Examples (from help)
Section titled “Examples (from help)”# Show full dependency graph for the 'food-types' LOV uc-apx deps food-types
# Show what page 1 depends on and what references it uc-apx deps 1
# Limit traversal to 2 hops uc-apx deps food-types --depth 2
# Disambiguate when an ID matches multiple kinds uc-apx deps breadcrumb --kind breadcrumbExample Output
Section titled “Example Output”Running against examples/brookstrut:
uc-apx --app-dir examples/brookstrut deps 1id: "1"name: Homekind: pagedependsOn[1]{kind,id,name,file,line,property,depth}: unresolved,/standard,"","",0,appearance.pageTemplate,1dependedBy[0]:JSON output
{ "id": "1", "name": "Home", "kind": "page", "dependsOn": [ { "kind": "unresolved", "id": "/standard", "property": "appearance.pageTemplate", "depth": 1 } ], "dependedBy": []}