npm upgrade
Home@changesets/config 1 → 2
1.7.0 → 2.3.1. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
@changesets/config 2.3.1 keeps every export lurq extracted, with the same argument counts.
- Removed
- 0
- Renamed
- 0
- Signature changes
- 0
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 0
Does this break your code?
Run this in your project. It compares both releases against the names your code actually imports, locally, with no account and nothing sent to lurq:
npx lurqrun check-upgrade --upgrade @changesets/config@1.7.0..2.3.1
To have your coding agent check upgrades like this before it writes them, connect lurq to Claude Code, Cursor, VS Code or Codex:
npx lurqrun
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 14, 2026. @changesets/config on lurq.