Zod 4

Post by dclowd9901 » Tue, May 20, 2025, 12:55 AM UTC

colinmcd wrote: post #125

Author here, AMA! Regarding the versioning: I wrote a fairly detailed writeup here[0] for those who are interested in the reasons for this approach. Ultimately npm is not designed to handle the situation Zod finds itself in. Zod is subject to a bunch of constraints that virtually no other libraries are subject to. Namely, the are dozens or hundreds of libraries that directly import interfaces/classes from Zod and use…

Post by pikelet » Tue, May 20, 2025, 1:21 AM UTC

rossant wrote: post #119

indigovole wrote: post #25

With yet another exciting new release of something reaching the top of HN, I would just like to urge devs to put a description of the project they're actually releasing and a link to the page describing the project in the release announcement. These announcements could be a valuable touchpoint for you to reach a whole new audience, but I can't remember a single one that starts with something like "exciting new releas…

I came here to say this. I clicked on the link and had no idea what this was about.

Post by ruined » Tue, May 20, 2025, 3:13 AM UTC

LMMojo wrote: post #184

All that text. So, so much text and not one single (maybe there was, but I fell asleep), not one single "Let me tell you what Zod is" paragraph. Lots of "Zod 4 is better than Zod 3" and "Here's what we pulled back, out, in, from Zod 2".

Post by root_axis » Tue, May 20, 2025, 3:35 AM UTC

skydhash wrote: post #148

Sammi wrote: post #140

Earlier quoted context omitted.

You use Zod to define all the schemas and types used in "your core domain". It is the base layer tool of your business logic and models, and for defining your interfaces. And yes it makes it possible to share all of this between the frontend and backend, which is a tremendous improvement in both correctness and in development productivity. You don't get anything remotely like this in any other backend frontend combo.

I get the wish to have that, but IMO, it's a flawed approach. The frontend and the backend are generally different domains. Initially, their model may look alike, but they will probably differs during the lifetime of the project as they serve different needs. That's why the shape of the data stored in the DB differs from the one involved in business logic, which differs from the DTOs, which can differs from the objec…

Post by rafram » Tue, May 20, 2025, 3:39 AM UTC

Dylan16807 wrote: post #170

rafram wrote: post #84

Earlier quoted context omitted.

let someArray = [1, 2, , 4]; console.log(as.numbers(someArray) === someArray); // => true for (let number of numbers) { // This should be safe because I know everything in the array is a number, right? console.log(number.toFixed(2)); // => TypeError: number is undefined } I mean, it's probably fine if you're only ever getting your data from JSON.parse(). But I would hesitate to use this in production.

> I mean, it's probably fine if you're only ever getting your data from JSON.parse(). So 90% of use cases?