npm upgrade
Homesmob 0 → 1
0.1.0 → 1.6.2. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
smob 1.6.2 removes or renames exports your code may import.
- Removed
- 5
- Renamed
- 0
- Signature changes
- 1
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 7
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 smob@0.1.0..1.6.2
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
Removed
Gone at runtime, with no replacement found under another name. Imports of these fail.
- baseMergerfunction
- cutObjectfunction
- isObjectDeeperThanfunction
- isSafeObjectfunction
- mergeArraysfunction
Signature changes
Still exported, but the number of arguments it reads changed.
- buildOptions1 → 0 arguments
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Sep 10, 2026. smob on lurq.