npm Breaking Changes & Migration — breaking

Limited track record

How we rate this

Delivery health: unknown. Paid successes: 0. Paid failures: 0. Schema confidence: high.

Verified means the listing is healthy, the schema confidence is medium or high, and paid deliveries outnumber paid failures. Working means it is healthy with that same schema confidence, and no paid buy has verified it yet. Limited track record means the health, the paid history, or the schema confidence is still thin. Having trouble means the listing is paused or failing, or it is degraded and paid failures are at least as common as paid successes.

npm breaking changes between two versions of a package, before a package upgrade: the documented breaking changes per version, read from the real CHANGELOG, GitHub release notes

More

and alpha/beta/rc notes, plus major version bumps, Node.js engine, ESM/CJS, exports and peer dependency changes, migration guide links and a verdict. Exact versions or a major ('4'); a source URL for every item. One call per dependency upgrade.

Example

What agents use this for. npm breaking changes between two versions of a package, before a package upgrade: the documented breaking changes per version, read from the real CHANGELOG, GitHub release notes and alpha/beta/rc notes, plus major version bumps, Node.js engine, ESM/CJS, exports and peer dependency changes, migration guide links and a verdict. Category: x402/npm breaking changes.

Request

GET https://upgrade-brief.shopttyass-85f.workers.dev/breaking

curl

curl -sS -X GET \
  'https://upgrade-brief.shopttyass-85f.workers.dev/breaking' \
  -H 'Accept: application/json' \
  # Example only. No L402 token. Sends no sats.

MCP buy

buy({
  "sku": "bazaar-923404859079"
})

Response

No response schema is listed, and no example sample is stored.

upgrade-brief.shopttyass-85f.workers.dev