aube why

• Usage: aube why [FLAGS] <PACKAGE>
• Aliases: w
• Effect: read-only

Print reverse dependency chains explaining why a package is installed

Read the workflow guide for context. Global options apply to this command too.

Arguments

• <PACKAGE> — Package name to search for (exact match against package names)

Flags

• -D --dev — Only follow chains that start at a devDependency

• -P --prod — Only follow chains that start at a production (or optional) dependency

  Aliases: --production

• --json — Output as JSON — an array of chain objects

• --long — Append each node's .aube/<dep_path> store path to the tree output

• --parseable — Tab-separated output: one line per chain, importer\tdep_type\tname@ver\t...

• -h --help — Print help

Examples

$ aube why debug
my-app@1.0.0 /home/user/project

dependencies:
express 4.19.2
└── debug 2.6.9
body-parser 1.20.2
└── debug 2.6.9

# Only follow chains starting at a devDependency
$ aube why --dev typescript

# Include each node's store path
$ aube why --long debug

# Tab-separated, one chain per line (pipe-friendly)
$ aube why --parseable debug

# JSON: an array of chain objects
$ aube why --json debug