fix: declare zod peer dependency#537
Open
lyzno1 wants to merge 1 commit into
Open
Conversation
|
@lyzno1 is attempting to deploy a commit to the codehike Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
codehike/blocksimportszodat runtime and exposes zod v3 schema types in its declarations, but the package currently only listszodindevDependencies. Package managers therefore may not install a compatible zod copy for consumers, and projects that already resolvezod@4can end up type-checkingcodehike/blocksagainst the wrong major version.This adds
zodas a peer dependency with the existing v3-compatible range and includes a patch changeset. The dev dependency remains so this package can still build and test itself.