home / skills / laurigates / claude-plugins / bun-outdated

bun-outdated skill

safe

/typescript-plugin/skills/bun-outdated

This skill checks Bun outdated dependencies and highlights current, wanted, and latest versions to guide safe updates.

npx playbooks add skill laurigates/claude-plugins --skill bun-outdated

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

941 B

---
model: haiku
description: Check for outdated dependencies
args: "[package]"
argument-hint: "Optional package name to check specific dependency"
allowed-tools: Bash, Read
created: 2025-12-20
modified: 2026-02-03
reviewed: 2025-12-20
name: bun-outdated
---

# /bun:outdated

Check which dependencies have newer versions available.

## Execution

```bash
bun outdated
```

## Output Format

Shows table with:
- Package name
- Current version
- Wanted version (within semver range)
- Latest version

## Follow-up Actions

**Update within ranges:**
```bash
bun update
```

**Update to latest (ignore ranges):**
```bash
bun update --latest
```

**Interactive update:**
```bash
bun update --interactive
```

**Update specific package:**
```bash
bun update <package>
```

## Post-check

1. Report count of outdated packages
2. Highlight major version updates (breaking changes)
3. Suggest `bun update` or `bun update --latest` based on findings

Overview

This skill checks a Bun project for outdated dependencies and reports which packages have newer versions available. It surfaces current, wanted, and latest versions so you can decide whether to update within semver ranges or move to the newest releases. The output is a simple table and includes guidance for next steps.

How this skill works

Run the bun outdated command to scan your lockfile and package manifest, producing a table with package name, current version, wanted version (within semver range), and latest version. The skill counts outdated packages and highlights major-version differences that may indicate breaking changes. It also suggests appropriate update commands based on the results.

When to use it

Before a scheduled dependency maintenance session to prioritize updates
After adding or modifying dependencies to verify newer releases exist
During a CI health check to generate a dependency status report
When preparing for a release to identify potentially breaking upgrades
Regularly as part of security or stability audits

Best practices

Run bun outdated from your project root so it reads the correct manifest and lockfile
Review major-version mismatches carefully; treat them as potential breaking changes
Prefer bun update for safe, semver-respecting updates and bun update --latest for full upgrades when you can handle breaking changes
Use interactive updates (bun update --interactive) to review and select updates selectively
After updating, run tests and linters to catch regressions introduced by updated packages

Example use cases

Quickly see which packages are behind before starting a dependency bump pull request
Decide whether to apply only patch/minor updates or to upgrade to latest major releases
Integrate into a CI job that fails or warns when critical dependencies are outdated
Interactive selective update session to upgrade only low-risk packages
Generate a summary report counting outdated packages and calling out breaking changes

FAQ

What does "wanted" mean in the output?

Wanted is the latest version that satisfies your declared semver range in package.json or equivalent; it respects your specified version constraints.

How do I update only one package?

Run bun update <package> to update a specific package while leaving others unchanged.