#zod

🔧 The Problem You've done everything right. Your User interface is clean, your API client...

With @panth977/routes, each Node.js endpoint is declared once with zod request and response schemas. That one declaration is the typed handler Express

TypeScript types vanish at runtime. With @panth977/functions, a function declares zod schemas for its input and output, and a SafeParse wrapper checks

A lot of frontend work starts with a JSON sample: an API response, a fixture, or an example payload...

Adding answer review to our session reports meant deciding, at the write, at the read and for every row that predates it, what happens when the new optional thing fails.

Why TypeScript types disappear at runtime, and how to use Zod to validate webhook payloads and form submissions at the boundary. Shape, semantics, and…

Zod 4's z.toJSONSchema() drops every .refine() and can't express transforms. Here's what the model sees, and a describe, validate, retry-once fix.

Nếu bạn từng deploy một service TypeScript với strict: true, không còn chỗ nào dùng any, CI xanh, rồi...

Mình từng review một incident lúc 2 giờ sáng: service Node.js crash hàng loạt với lỗi TypeError:...

Disclosure: I built the converter used in this post. The Zod code below is useful without...

"Validate at the edges" is one of those phrases everyone agrees with and nobody finishes. I wrote...

TypeScript checks your code before it runs. Once it ships, the types are gone. The compiler cannot...