ember
Documentation menuembr 0.13.0

Commands

embr tree & embr why

Last updated November 2, 2026

embr tree [--depth <n>]
embr why <package>

Show the dependency graph that embr install installed. Both commands only read.

embr tree#

roblox
├── chief/core@0.2.0 as 'Core'
├── chief/traits@0.2.0
│   ├── chief/bin@0.2.0
│   └── chief/core@0.2.0
└── chief/bin@0.2.0 (dev)
roblox_server
└── chief/lifecycles@0.3.0
    └── chief/core@0.2.0
  • The top of the tree is each entry of [dependencies] and [dev-dependencies]. A dev dependency has (dev).
  • Each package shows as scope/name@version. When the alias is not the short name, the alias follows, because the alias is the name of the link file.
  • When the direct dependencies install in more than one environment, each environment gets a heading. A dependency with target installs its tree in that environment.
  • A package with dependencies that shows a second time gets (*), and its dependencies do not show again. This is what cargo tree does.
  • --depth sets the number of levels under the direct dependencies. --depth 0 shows the direct dependencies only.

embr why#

chief/core@0.2.0 in roblox
  ember.toml > chief/core@0.2.0 as 'Core'
  ember.toml > chief/traits@0.2.0 > chief/core@0.2.0
chief/core@0.2.0 in roblox_server
  ember.toml > chief/lifecycles@0.3.0 > chief/core@0.2.0

embr why shows each path from ember.toml down to a package, one path on each line. The package is a scope/name, or the alias that a dependent gives it. When the package installs in more than one environment, each copy gets its own heading. A path from a dev dependency starts with ember.toml [dev-dependencies]. A package that is not installed is an error.

Behavior#

  • ember.lock records no edges, so both commands read what the install wrote: ember.lock, and the manifest in the folder of each installed package. An edge that [overrides] redirects leads to the replacement. A workspace member's dependencies come from its own ember.toml.
  • Without ember.lock, or with a package folder missing, the command stops and asks you to run embr install. It also stops when ember.toml has a dependency that ember.lock does not have yet.
  • A dependency removed from ember.toml leaves the tree at once, before the next install.

See also#