npm upgrade
Homevalibot 0 → 1
0.42.1 → 1.5.0. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
valibot 1.5.0 removes or renames exports your code may import.
- Removed
- 1
- Renamed
- 0
- Signature changes
- 8
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 77
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 valibot@0.42.1..1.5.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
Removed
Gone at runtime, with no replacement found under another name. Imports of these fail.
- defaultobject
Signature changes
Still exported, but the number of arguments it reads changed.
- nullable1 → 2 arguments
- nullableAsync1 → 2 arguments
- nullish1 → 2 arguments
- nullishAsync1 → 2 arguments
- optional1 → 2 arguments
- optionalAsync1 → 2 arguments
- undefinedable1 → 2 arguments
- undefinedableAsync1 → 2 arguments
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Sep 10, 2026. valibot on lurq.