Zod 4 support

[channyeintun]

Need support for Zod 4 and @zod/mini
Zod 4 beta and @zod/mini beta are out recently. Currently, resolver doesn't work with Zod 4 and @zod/mini.

[semet]

I have added related discussion in React Hook Form Repo. Looking forward for the recent update to this...

[wenerme]

xref colinhacks/zod#4074

[ukuq]

I found a solution and intend to submit a PR, but I noticed the version number on GitHub is much lower than the one on npm. Not sure why - maybe the author hasn't open-sourced the latest code? Who knows.
Below is my solution:

Object.defineProperty(ZodError.prototype, "errors", {
    get() {
        return this.issues;
    },
    enumerable: true,
    configurable: true,
});

const form = useForm<{ [x: string]: never }>({
    resolver: zodResolver(FormSchema),
    defaultValues: data as { [x: string]: never },
});

[ukuq]

I found a solution and intend to submit a PR, but I noticed the version number on GitHub is much lower than the one on npm. Not sure why - maybe the author hasn't open-sourced the latest code? Who knows. Below is my solution:

Object.defineProperty(ZodError.prototype, "errors", {
    get() {
        return this.issues;
    },
    enumerable: true,
    configurable: true,
});

const form = useForm<{ [x: string]: never }>({
    resolver: zodResolver(FormSchema),
    defaultValues: data as { [x: string]: never },
});

It seems this is controversial, so I'll close the PR for now.

[BLucky-gh]

For anyone who needs zod v4 support now, you can use the standard schema resolver since zod v4 supports standard schema

[raptoria]

sorry, a bit of a n00b here. What is the standard schema resolver? Can you provide a link?
I just upgraded to zod 4. Does this solve the issue of seeing an Uncaught in Promise error when my form first loads (because validation fails)? I thought @hookform/resolvers/zod already supported and used safeParse by default since V.4 so I'm confused as to why I see a promise error (I'm using V.5.0)

[igomonteiro]

@raptoria can you try something like this?

const form = useForm<z.infer<typeof SignInSchema>>({
    resolver: standardSchemaResolver(SignInSchema),
    defaultValues: {
      email: "",
      password: "",
    },
  });

instead of zodResolver, use the standardSchemaResolver from @hookform/resolvers/standard-schema.
its working for me, maybe work for u as well.

[semet]

sorry, a bit of a n00b here. What is the standard schema resolver? Can you provide a link? I just upgraded to zod 4. Does this solve the issue of seeing an Uncaught in Promise error when my form first loads (because validation fails)? I thought @hookform/resolvers/zod already supported and used safeParse by default since V.4 so I'm confused as to why I see a promise error (I'm using V.5.0)

standard schema resolver is any standard schema package that is not in the list of schema supported by this package. You can use zod v4 combined with standardSchemaResolver like so

import { standardSchemaResolver } from '@hookform/resolvers/standard-schema';
import { z } from "zod"

const form = useForm<z.infer<typeof someZodSchemaVersion4>> ({
    resolver: standardSchemaResolver(someZodSchemaVersion4)
})

this works fine, but the downside is u have to enforce the generic in the useForm<typeof someZodSchemaVersion4> while in the latest version of the react-hook-form/resolvers, the type shuld be automatically infered based on the schema you pass.

[semet]

@raptoria can you try something like this?

const form = useForm<z.infer>({
resolver: standardSchemaResolver(SignInSchema),
defaultValues: {
email: "",
password: "",
},
});
instead of zodResolver, use the standardSchemaResolver from @hookform/resolvers/standard-schema. its working for me, maybe work for u as well.

it works fine, but the downside is we have to use the old style of manually enforcing the type of the data in the generic. While in the latest version of react-hook-form/resolvers, it should be automatically infered based on schema you passed in.

[raptoria]

thanks all for the replies! hmm..for some reason the standardSchemaResolver breaks the validation I had working for my discriminated unions. But it seems to work with my other, simpler forms