npm upgrade
Hometldts 4 → 5
4.0.6 → 5.7.112. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
tldts 5.7.112 changes how many arguments some functions take.
- Removed
- 0
- Renamed
- 0
- Signature changes
- 5
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 1
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 tldts@4.0.6..5.7.112
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.
- getDomain2 → 1 arguments
- getHostname2 → 1 arguments
- getPublicSuffix2 → 1 arguments
- getSubdomain2 → 1 arguments
- parse2 → 1 arguments
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 25, 2026. tldts on lurq.