Zod 4.5 adds in-process schema compilation and cuts schema memory use

The new release speeds up validation and makes schema objects far smaller, reducing the cost of checking untrusted data in TypeScript.

Zod 4.5 added in-process schema compilation, a much smaller memory footprint for schema objects, and several utility methods that matter for teams using it to validate untrusted data in TypeScript. The new z.compile() turns a schema into a validator that runs about three to nine times faster, and it can be enabled globally with an import or a node --import flag instead of a build-time codegen step. Zod also cut the retained size of a bare z.string() from 7.5kb to 784 bytes, while safeParse() became cheaper on failures by skipping stack-trace capture. The release restored z.deepPartial(), added .exactPartial(), .creditCard(), .input()/.output(), recursive-cycle support, and eight new error locales, then 4.6 followed with .validate(), property checks on class instances, extra JSON Schema keywords, and a fix for the recursive-schema memory regression introduced in 4.5. In the release benchmark, compiled Zod reached 47.5M ops/sec on Moltar parseSafe, and the 4.5 boolean-only benchmark showed that Typia and ArkType were still ahead on that path.