thank you!!

yaaasssss

no but they could probably benefit from it!

Standard JSON Schema A standardized JSON Schema representation that preserves inferred type information

Visit the website to see the fulltext spec, FAQs, integration examples, and more standardschema.dev/json-schema

If you implement or integrate with the spec, don't forget to submit a PR adding yourself to the website ✌️

The following schema libraries have implemented day-one support for the spec 👇

Note the minimum versions (these we're all released in the last few weeks)

This takes the onus off the end user to properly convert their schemas correctly to the format expected by some consuming library, eliminating a swath of potential footguns & unnecessary DX complexity

It puts control in the hands of the *consuming library*. Given a spec-compliant entity, they can:

• extract a JSON representation of either its input or output type
• control the *draft version* of the produced JSON Schema
• pass library-specific config

This is the first ecosystem-wide standard representation that unifies runtime and static type information

Essentially "JSON Schema with inferred types" — which unlocks totally new APIs for frameworks & AI tools

Introducing ✨ Standard JSON Schema ✨

It's a sister spec to Standard Schema that provides a common interface for any entity that can be converted to JSON Schema

wish I'd thought of this 3 days ago 🫠

thanks Ryan!!

right!?!?

thanks josh! really looking forward to having you play with it!

Pullfrog The ultimate agentic GitHub bot. Powered by your favorite coding agents.

check out the website for a more detailed explanation, and to join the waitlist. we'll be letting people in over the next few weeks! pullfrog.com

Pullfrog is the "agent x GitHub" integration I wish existed

🐸 can plan, review, and implement PRs (and more)
🐸 GitHub-first (no new UI)
🐸 agent-agnostic (bring your own agent / API key)
🐸 runs in GitHub Actions
🐸 configurable: custom per-trigger prompts, automations, etc

we're taking a stab at a problem we're familiar with: improving the DX of iterating on code (with AI) inside of GitHub.

having closed 6000 issues and PRs on Zod/ArkType over the last 5 years—we have thoughts.

sounds fake but I'm starting a company with my nemesis David E. ArkType

and our first hire is @andarist.bsky.social

and our first product is now in beta :)

as you said, "decode" and "parse" are essentially synonymous. encoding is the new thing here, and it's the inverse of parse. but in anycase, this isn't something I just came up with: see io-ts and Effect Schema.

Third Party Modules | Deno A hosting service for Deno scripts.

starting with Zod 4, Zod is published to JSR but not deno.land/x

Introducing Zod Codecs

for a more detailed technical breakdown of codecs, read the associated blog post 👍 colinhacks.com/essays/intro...

including...

✅ stringToNumber
✅ stringToInt
✅ stringToBigInt
✅ numberToBigInt
✅ isoDatetimeToDate
✅ epochSecondsToDate
✅ epochMillisToDate
✅ jsonCodec
✅ utf8ToBytes
✅ bytesToUtf8
✅ base64ToBytes
✅ base64urlToBytes
✅ hexToBytes
✅ stringToURL
✅ uriComponent

Codecs | Zod Bidirectional transformations with encode and decode

instead of providing first-party APIs for commonly-needed codecs, Zod is taking a page from shadcn

fully-tested versions of 16 commonly-needed codecs are available on the new Codecs page. you're encouraged to copy/paste/customize them as needed 👍
zod.dev/codecs

Codecs is useful when mapping data between two different domains. for instance, when converting data in your Node.js backend from a rich JavaScript representation (Dates, BigInts, Maps, Sets, etc) into a JSON-serializable format (ISO datetimes, arrays, etc)

these methods are intended for use cases involving data *conversion*, not *validation* (though they do that too). so if you pass in an input of an unexpected type, you'll get a TypeScript error.

"how does .decode() differ from .parse()?"

good question! they're identical at runtime, but their type signatures differ in an important way.

unlike .parse()—which accepts `unknown` input—decode and encode expect strongly-typed inputs

It is coupled with the addition of new methods (available on all Zod schemas)

.decode() — "forward" parsing
.encode() — "reverse" parsing

Introducing Zod 4.1 and its flagship feature: codecs.

z.codec() is a new API for defining *bi-directional transformations* in Zod

in the absence of an existing convention, I'm adding these three fields to Zod's package.json.

making this stuff auto-discoverable would resolve one of the biggest usability issues with today's agents/IDEs. a simple convention here will go a long way! 🤘

sounds like you found an alternative but the answer is "not at all". MIT license, go ham :)

very nice 🤩