npm upgrade
Homecontent-type 1 → 2
1.0.5 → 2.1.0. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
content-type 2.1.0 changes how many arguments some functions take.
- Removed
- 0
- Renamed
- 0
- Signature changes
- 1
- 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 content-type@1.0.5..2.1.0
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
Signature changes
Still exported, but the number of arguments it reads changed.
- parse1 → 2 arguments
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Sep 18, 2026. content-type on lurq.