npm upgrade
Homezod 3 → 4
3.25.76 → 4.6.5. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
zod 4.6.5 removes or renames exports your code may import.
- Removed
- 28
- Renamed
- 2
- Signature changes
- 1
- Types removed
- 0
- Newly deprecated
- 2
- Added
- 184
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 zod@3.25.76..4.6.5
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.
- BRANDobject
- DIRTYfunction
- EMPTY_PATHobject
- OKfunction
- ParseStatusclass
- ZodBrandedclass
- ZodEffectsclass
- ZodNativeEnumclass
- ZodParsedTypeobject
- ZodPipelineclass
- ZodTransformerclass
- addIssueToContextfunction
- datetimeRegexfunction
- defaultErrorMapobject
- effectobject
- getParsedTypeobject
- isAbortedfunction
- isAsyncobject
- isDirtyfunction
- isValidfunction
- lateobject
- makeIssuefunction
- obooleanfunction
- onumberfunction
- ostringfunction
- pipelineobject
- quotelessJsonfunction
- transformerobject
Renamed
The old name is gone; the same implementation is exported under the new one.
- SchemaZodType
- ZodSchemaZodType
Signature changes
Still exported, but the number of arguments it reads changed.
- custom1 → 2 arguments
Newly deprecated
Still exported in 4.6.5, marked deprecated.
- ZodCUID
- ZodIssueCode
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Sep 21, 2026. zod on lurq.