Typescript error since Zod 4.0.11+: is missing the following properties from type 'TSchema': params, static, [Kind]

[jamesst20]

Description

  import type { SuperValidated, Infer } from "sveltekit-superforms";
  import type { FormSchema } from "$routes/.../schemas";
  type Props = { form: SuperValidated<Infer<FormSchema>>; };
  let { form, ... }: Props = $props();

Since Zod 4.0.11, SuperValidated<Infer<FormSchema>>; raises a Typescript error:

Type 'ZodObject<{ id: ZodOptional<ZodNumber>; protocol: ZodLiteral<"rtsp">; name: ZodString; host: ZodString; port: ZodCoercedNumber<unknown>; username: ZodString; password: ZodOptional<...>; path: ZodString; }, $strip>' does not satisfy the constraint 'Schema'.
  Type 'ZodObject<{ id: ZodOptional<ZodNumber>; protocol: ZodLiteral<"rtsp">; name: ZodString; host: ZodString; port: ZodCoercedNumber<unknown>; username: ZodString; password: ZodOptional<...>; path: ZodString; }, $strip>' is not assignable to type 'TSchema | Schema<any, any, any, "">'.
    Type 'ZodObject<{ id: ZodOptional<ZodNumber>; protocol: ZodLiteral<"rtsp">; name: ZodString; host: ZodString; port: ZodCoercedNumber<unknown>; username: ZodString; password: ZodOptional<...>; path: ZodString; }, $strip>' is missing the following properties from type 'TSchema': params, static, [Kind]ts(2344)

Workaround

Downgrading to Zod 4.0.10 resolves the issue.

Additional notes

The error is also present in the next versions of Zod: 4.0.11, 4.0.12, 4.0.13 (latest)

[emmabyte]

I am also having this issue. I had to downgrade to zod 4.0.10 in order to resolve the issue.

[apoorvmote]

I am also having same issue but I didn't downgrade. Its type issue and my app is not breaking. But please fix it asap.

[Greenheart]

Resolving this issue seems to require changes to the types of the zod4() and zod4Client() helpers in sveltekit-superforms.

Here's the diff between zod@4.0.10 and zod@4.0.11: colinhacks/zod@v4.0.10...v4.0.11

This change in the core API seems like it could have something to do with the new error: colinhacks/zod@v4.0.10...v4.0.11#diff-6406e7012723406c630516d4216f7b23a0418cfb6e54774eb1ac049f05b2aba2

Perhaps the new resulting schema is a slightly different type which is not expected by zod4() and zod4Client().

[rebasecase]

Also in zod 4.0.14.

I'd love to fix this, but fixing type meta-language behaviour is way beyond my capabilities at current

[jerriclynsjohn]

Yeah, this is an issue for 4.0.14. Downgrading to 4.0.10 fixes this.

[ciscoheat]

I wish I could test this properly, but there are dependencies that cannot handle Zod 4 yet, until then I cannot build the project with Zod npm version ^4. I hope it will be fixed as soon as possible: StefanTerdell/zod-to-json-schema#178

[apoorvmote]

Everyone keeps saying Downgrading to 4.0.10 has fixed this problem but I downgraded from 4.0.10 to all the way till 4.0.0 and it didn't fix my problem. The type error persists even with downgrade. I restarted my VS Code. Rebooted my computer. The type error never goes away. Also my app doesn't break on any upgrade upto 4.0.14 so far. So I am using the latest version today. But please fix it as soon as possible.

[knd775]

Everyone keeps saying Downgrading to 4.0.10 has fixed this problem but I downgraded from 4.0.10 to all the way till 4.0.0 and it didn't fix my problem. The type error persists even with downgrade. I restarted my VS Code. Rebooted my computer. The type error never goes away. Also my app doesn't break on any upgrade upto 4.0.14 so far. So I am using the latest version today. But please fix it as soon as possible.

You're likely setting it to ^4.0.10, which allows it to use a later version if it's already downloaded.

[muqiuhan]

Yes, locking zod version 4.0.10 can fix this issue!

[apoorvmote]

Thanks for the help guys. I fixed the issue temporarily by downgrading to 4.0.10 intead of ^4.0.10

[amlcx]

yep, +1