|
|
|
|
|
|
by robertlagrant
391 days ago
|
|
|
> The approach I ended up using is analogous to what Golang does. In essence a given package never publishes new breaking versions: they just add a new subpath when a new breaking release is made. In the TypeScript ecosystem, this means libraries can configure a single peer dependency on zod@^3.25.0 and support both versions simultaneously by importing what they need from "zod/v3" and "zod/v4". It provides a nice opt-in incremental upgrade path for end-users of Zod too. This is extremely sensible. And it means you can provide security updates for older versions, just all in the same codebase's releases. |
|
|