Colin McDonnell

@mikearnaldi I'm a little fuzzy on your recommendation here. Do you think this should use the continuation approach is better, or are you happy with the two-method API? If you're...

> I had a quick look, and it seems zod will always return a Promise in "async mode"? So two seperate apis makes sense. That's correct, though liable to change...

@RobinTail Yes, this is how plugins are going to work. The Vue (v2) and Dayjs plugin systems are the prior art here. Zod has always been hackable - that's why...

This is working for me on Bun v0.3 on an M1 Mac. @nikitavoloboev are you still experiencing this?

Unless I'm missing something specific about your situation, this is precisely how workspaces are supposed to work. If all of your packages share dependencies, they get hoisted to the root...

This happens because, at the point where `z.object()` is called, `schema` could be any subtype of `ZodTypeAny`. Because `any` extends `undefined`, Zod is adding a question mark to the inferred...

Inference is certainly full of mysteries. Perhaps @Andarist or another kindly expert on TypeScript internals has a better understanding here? > anything but undefined Unfortunately this isn't a type that...

There is not, though I'll leave this issue open to gauge interest in some system of "hooks" that could be used to support OpenTelemetry.

Thanks, love this! I'm going to merge this into the `v4` branch because the design of error maps will change quite dramatically in Zod 4. I'll also doing a big...

This is true. It was a tradeoff I made so I could ship `z.coerce` without a breaking change. Because `ZodString` has no generics, there's no way for me to change...