upgrade-deps

Upgrade Deps

Upgrade dependencies safely by understanding usage before changing versions.

Workflow

Audit → Research → Upgrade → Verify → Clean up

1. Audit

Understand current usage before changing anything:

tl parallel \
  "npm=tl npm <package>" \
  "search=tl search '<package-name>'" \
  "deps=tl deps <file>"

2. Research

Check what changed between versions:

tl parallel "browse=tl browse <changelog-url>" "docs=tl context7 <package> 'migration guide'"

Look for: removed APIs, renamed functions, changed defaults, new peer deps.

3. Upgrade

Apply the version bump:

# Update package.json and install
tl diff --breaking         # Detect signature mismatches in wrapper files
tl snippet <symbol> <file> # Check each usage site against new API

4. Verify

tl parallel \
  "test=tl run '<test command>'" \
  "testmap=tl test-map <file>" \
  "guard=tl guard"

5. Clean up

Remove old compatibility code:

tl parallel "unused=tl unused" "search=tl search '<old-version>'"

Decision tree

Upgrade request → How big is the version jump?
  ├─ Patch (1.2.3 → 1.2.4) → Light check
  │   → tl npm to confirm, upgrade, tl run tests
  ├─ Minor (1.2 → 1.3) → Standard check
  │   → tl search for usage, tl browse changelog
  │   → Upgrade, tl run tests
  └─ Major (1.x → 2.x) → Full audit
      → tl search for all usage sites
      → tl browse changelog + migration guide
      → tl snippet on every consumer
      → Upgrade, tl diff --breaking, tl run tests
      → tl unused to clean up compat code

Tips

• tl npm output includes the changelog URL — use it with tl browse
• Use tl context7 for popular frameworks (React, Next.js, etc.) — it has migration guides
• Always check for changed peer dependencies after major upgrades
• Run tl unused after removing compatibility code — catch leftover dead exports
• Never upgrade a major version without reading the migration guide first