Zod v4 Beta Support

[kylekirkby]

Hi all,

Any chance anyone has put any thought into supporting Zod v4 considering the awesome perf boost that v4 offers

It would be great to get this project a beta version out which implements the breaking changes introduced in v4.

https://v4.zod.dev/v4

Cheers!

Kyle

[tadhglewis]

Is this needed as Zod natively supports JSON schema now? https://v4.zod.dev/json-schema

[StefanTerdell]

I was hoping to use v4 to break away from the major/minor-lockstep versioning into actual semver, and refactor the entire project with some much needed breaking changes, but as tadhglewis mentioned the native support kinda makes that project moot. On the other hand, v4 is still in beta, and I'm not actually sure what level of customization etc. the built-in functionality offers. In other words, there might be a raison d'être for a separate library like this, but we'll have to wait and see.

In the meantime I won't be putting any of my time or energy into it.

[AndrewIngram]

It might be useful just as a compat step to make upgrading easier, i.e. it'd be nice to be able to upgrade Zod without upgrading all the places we currently use zod-to-json-schema (at the same time). But appreciate that's not exactly a strong motivation for you to put work in here.

[colinhacks]

I strongly encourage you to bump the version and continue maintaining this! Many people will want a hassle-free migration path, while also getting the perf benefits of Zod 4. The new z.toJSONSchema is a totally different set of options. I'm trying to keep it extremely minimal, and point people towardsoverride for the vast majority of customization needs.

Ultimately there aren't a ton of changes in terms of schema types & internal structure so I don't think a refactor would be too painful. 😅

[wenerme]

xref colinhacks/zod#4074

[sqikerz]

@StefanTerdell have you decided if bumping the version was worth it yet? I'm beginning to realize that many libraries are forcing the new Zod v4, which is incompatible with this package. The new toJSONSchema has practically no native support to openApi formatting, which I believe is used by many projects that use this library.

[StefanTerdell]

I'm low key cooking something, but I don't have much time to spend on it. Hopefully I'll have something pretty cool to share during the summer.

[phshah95]

@StefanTerdell lmk if you need help

[AviVahl]

zod@4.0.5 (stable) is out. the peerDependency range of this package still only specifies v3:

zod-to-json-schema/package.json

Line 64 in 3893d85

"zod": "^3.24.1"

[Uanela]

I am building an Express.js Framework and just fall on the need for this also and then found out through this issue that zod 4 has a func to transform to jsonSchema now just need to make a subtle check to see if the end developer is using zod 4 or zod 3.

Btw would be cool to have this feature (support to v4) on this package.

[kaechele]

Two comments here:

1. peerDependency specifying v3 only is formally correct. This package imports zod v3 from "zod" right now and not from "zod/v3" as would be required when using v4 of the package.
2. I think this project definitely has continued usefulness due to the purposefully limited scope of the native v4 JSONSchema implementation in zod. zod/v4: Non JSONSchema representable types used with default() will always initialize to empty object {} ciscoheat/sveltekit-superforms#617 looks like an issue that will need to be solved with a custom implementation either way, so it might as well be in a library like this. I'm assuming Superforms won't be the only project that needs more control over how JSONSchema is generated from zod objects.

[nicolasembleton]

Yes. Most likely everyone will move to Zod V4's native capabilities.

In case anyone does not want to do the migration and still needs V4 support for this library, I took a gander at updating this library to V4 and tried to keep it compatible with V3. All tests pass and I'm using it in a project successfully so it should work fine, but if it doesn't feel free to add an issue there. I currently use it successfully, installed directly via github.

If you use directly via github, you can use:

pnpm add Alcyone-Labs/zod-to-json-schema#dist
# make sure to use the dist branch as I pushed all built artefacts there

This should work with any other Node Package Manager.

The repo is here:
https://github.com/Alcyone-Labs/zod-to-json-schema