embr outdated

embr outdated [--refresh]

Lists the dependencies that have a newer release. It only reads: it installs nothing, and it does not change ember.toml or ember.lock.

Output#

Each row is a dependency that is behind, in four columns:

Column	What it shows
Dependency	the [dependencies] key and the package, such as signal (acme/signal)
Current	the version ember.lock holds, or - before the first install
Wanted	the newest release that the version requirement allows
Latest	the newest release of the package

A line under the table counts the dependencies that are behind. embr install moves a dependency to Wanted. To go past Wanted, raise the requirement with embr add <name> --version <req>.

When nothing is behind, it prints Every dependency is up to date.

Behavior#

• A dependency is behind when Latest is newer than Current. A dependency with nothing in ember.lock yet counts too, so a first look shows what an install would take.
• Each dependency is checked against its own index: Ember's registry, a key under [indices], forest, or local.
• The picks follow the project's [target], and a dependency's own target if it sets one, the same way an install picks.
• Workspace members are left out: the member in the workspace is the copy you develop, so it has no release to be behind.
• Indices up to 5 minutes old are used as they are. --refresh fetches them first.

See also#

• embr install to take the Wanted versions.
• embr add to change a version requirement.