bun why

​

Usage

bun why <package>

​

Arguments

• <package>: The name of the package to explain. Supports glob patterns like @org/* or *-lodash.

​

Options

• --top: Show only the top-level dependencies instead of the complete dependency tree.
• --depth <number>: Maximum depth of the dependency tree to display.

​

Examples

bun why react

react@18.2.0
  └─ my-app@1.0.0 (requires ^18.0.0)

bun why "@types/*"

@types/react@18.2.15
  └─ dev my-app@1.0.0 (requires ^18.0.0)

@types/react-dom@18.2.7
  └─ dev my-app@1.0.0 (requires ^18.0.0)

bun why express --top

express@4.18.2
  └─ my-app@1.0.0 (requires ^4.18.2)

bun why express --depth 2

express@4.18.2
  └─ express-pollyfill@1.20.1 (requires ^4.18.2)
     └─ body-parser@1.20.1 (requires ^1.20.1)
     └─ accepts@1.3.8 (requires ^1.3.8)
        └─ (deeper dependencies hidden)

​

Understanding the Output

• The package name and version being queried
• The dependency chain that led to its installation
• The type of dependency (dev, peer, optional, or production)
• The version requirement specified in each package’s dependencies