bun outdated: List Upgradable Dependencies
bun outdated prints a table of installed dependencies that have newer versions, showing current, wanted (in-range), and latest.
bun outdated is read-only: it tells you what could be upgraded without changing anything. It pairs with bun update to decide which bumps to take.
What it does
bun outdated compares installed versions against the registry and prints a table with Current (installed), Update/Wanted (newest within the package.json range), and Latest (newest published) for each dependency that is behind. It makes no changes.
Common usage
bun outdated
bun outdated react # one package
bun outdated "@types/*" # filter by patternOptions
| Argument | What it does |
|---|---|
| (none) | List all outdated dependencies |
| <package> | Limit to a specific dependency |
| <pattern> | Glob filter, e.g. "@types/*" |
In CI
Run bun outdated in a scheduled job to surface drift, or as an informational (non-blocking) step on PRs. Because it is read-only it never breaks --frozen-lockfile. To act on it, follow with bun update on a branch, then let CI install and test the new lockfile.
Common errors in CI
"No lockfile found" or an empty table when packages are clearly behind usually means dependencies were not installed; run bun install first. Network errors reaching the registry show as fetch failures; a private registry needs auth in bunfig.toml. The Wanted column matching Current means your ranges are too tight to absorb the update without editing package.json.