Honestly, it made things worse for me. JavaScript isn’t a statistical typed language and TypeScript already is something, where due to compiler issues I just use “any”.
Zod has its conventions and JavaScript ain’t Java.
So Zod is also hard to read and debug. It is type conversion to type conversion - bloat, not JavaScript.
Even Pydantic looks tamed compared to Zod.
So how do you use it? Which conventions? Only for validation at certain steps? APIs?
I stopped using TanStack because it got to meta for me and AI as well.
Tests are needed anyway, I rely on TypeScript only now.
I don't love Pydantic, though. It's probably a skill issue, but it just feels messier/clunkier than Zod's parsing options.
Uh, maybe you're not seeing the benefit due to this. My codebase bans "any" and Zod is great for runtime data validation.
TypeScript already is something, where due to compiler issues I just use “any”.
Why use TypeScript at all? So Zod is also hard to read and debug.
Rebuttal: no it is not. Poorly written code is hard to read and debug; TypeScript in particular is hard to read and debug when you explicitly type things as `any`.