Dependency Upgrade One-by-One
Upgrade a single outdated package per iteration, fix breakages, and commit — safer than bulk npm update.
Kickoff prompt
Start the "Dependency Upgrade One-by-One" loop.
Goal: critical outdated deps are upgraded with green tests
Max iterations: 15
Between iterations run: npm outdated && npm test && npm run build
Exit when: npm outdated shows no critical packages left or user stops
Step 1: Pick one outdated package, upgrade it, fix breakages, commit, and stop. One package per iteration.
Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.Basic information
Category
Maintenance
Goal
critical outdated deps are upgraded with green tests
Max iterations
15
Check command
npm outdated && npm test && npm run build
Exit when
npm outdated shows no critical packages left or user stops
Supported agents
Cursor
Steps
- 1
Pick one package
Run npm outdated. Pick the highest-impact outdated package (one only). Note its current and target version.
npm outdated - 2
Upgrade and fix
Upgrade that single package. Fix type errors, API changes, and test failures caused by the bump.
npm test && npm run build - 3
Commit bump
Commit with message like chore(deps): bump <package> to <version>.
More Maintenance loops
Docs Sync After Edits
After code changes, find affected docs and update README, API references, and inline comments to match.
Knip Until Clean
Find and remove dead exports, unused files, and orphan dependencies — loop until knip reports clean.
Dependency Audit Weekly
Weekly loop to check outdated dependencies, propose safe upgrades, and open a summary.
Security Audit Weekly
Weekly npm audit scan, triage vulnerabilities by severity, and propose or apply safe patches.