Breaking Changes & Migration Data
What breaks when you upgrade a package, and what to use instead - from official docs.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
What breaks when you upgrade a package, and what to use instead - from official docs.
Server tool list (3)
Raw names from tools/list. Only developers need these.
| list_packages | List every package with breaking-change data available, including tracked versions and how many breaking changes each has. Call this first if you are unsure whether a package is covered. |
| get_breaking_changes | Get breaking changes for a package upgrade: removed APIs with their replacements and the reason for each, changed defaults, behavior changes, known incompatible dependencies, official source URL, and codemod/automated-fix commands. Omit `version` to get every tracked version. Use this instead of relying on training data, which may predate the release. |
| check_upgrade_safety | Given a package and the version you are upgrading TO, return a concise checklist an agent can act on: the count of breaking changes, the highest-risk removals, whether automated codemods exist, and the recommended upgrade path. Use before performing an upgrade. |