Colin McDonnell ๐ Zod
@colinhacks.com
๐ Creator of Zod, tRPC (v0)
๐ฎ OSS Fellow @ Clerk
๐ฆ Friendly neighborhood TypeScript nerd
๐ง๐ผโ๐ป Prev @ Bun, EdgeDB, YC, MIT
๐ฎ OSS Fellow @ Clerk
๐ฆ Friendly neighborhood TypeScript nerd
๐ง๐ผโ๐ป Prev @ Bun, EdgeDB, YC, MIT
no but they could probably benefit from it!
December 16, 2025 at 3:39 PM
no but they could probably benefit from it!
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 โ๏ธ
If you implement or integrate with the spec, don't forget to submit a PR adding yourself to the website โ๏ธ
Standard JSON Schema
A standardized JSON Schema representation that preserves inferred type information
standardschema.dev
December 15, 2025 at 11:28 PM
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 โ๏ธ
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)
Note the minimum versions (these we're all released in the last few weeks)
December 15, 2025 at 11:28 PM
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)
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
December 15, 2025 at 11:28 PM
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
โข extract a JSON representation of either its input or output type
โข control the *draft version* of the produced JSON Schema
โข pass library-specific config
December 15, 2025 at 11:28 PM
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
โข 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
Essentially "JSON Schema with inferred types" โ which unlocks totally new APIs for frameworks & AI tools
December 15, 2025 at 11:28 PM
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
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
It's a sister spec to Standard Schema that provides a common interface for any entity that can be converted to JSON Schema
December 15, 2025 at 11:28 PM
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
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 ๐ซ
hello world! we're building the ultimate integration layer between GitHub and your favorite coding agents. coming early 2026.
send me a DM containing the ๐ธ emoji to join the waitlist :)
send me a DM containing the ๐ธ emoji to join the waitlist :)
December 12, 2025 at 8:46 PM
wish I'd thought of this 3 days ago ๐ซ
thanks josh! really looking forward to having you play with it!
December 10, 2025 at 11:29 PM
thanks josh! really looking forward to having you play with it!
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
The ultimate agentic GitHub bot. Powered by your favorite coding agents.
pullfrog.com
December 10, 2025 at 5:33 PM
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
๐ธ 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
December 10, 2025 at 5:33 PM
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
๐ธ 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.
having closed 6000 issues and PRs on Zod/ArkType over the last 5 yearsโwe have thoughts.
December 10, 2025 at 5:33 PM
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.
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 :)
and our first hire is @andarist.bsky.social
and our first product is now in beta :)
December 10, 2025 at 5:33 PM
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 :)
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.
August 27, 2025 at 8:12 PM
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.
starting with Zod 4, Zod is published to JSR but not deno.land/x
Third Party Modules | Deno
A hosting service for Deno scripts.
deno.land
August 27, 2025 at 8:08 PM
starting with Zod 4, Zod is published to JSR but not deno.land/x
for a more detailed technical breakdown of codecs, read the associated blog post ๐ colinhacks.com/essays/intro...
Introducing Zod Codecs
colinhacks.com
August 26, 2025 at 12:44 AM
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
โ stringToNumber
โ stringToInt
โ stringToBigInt
โ numberToBigInt
โ isoDatetimeToDate
โ epochSecondsToDate
โ epochMillisToDate
โ jsonCodec
โ utf8ToBytes
โ bytesToUtf8
โ base64ToBytes
โ base64urlToBytes
โ hexToBytes
โ stringToURL
โ uriComponent
August 26, 2025 at 12:44 AM
including...
โ stringToNumber
โ stringToInt
โ stringToBigInt
โ numberToBigInt
โ isoDatetimeToDate
โ epochSecondsToDate
โ epochMillisToDate
โ jsonCodec
โ utf8ToBytes
โ bytesToUtf8
โ base64ToBytes
โ base64urlToBytes
โ hexToBytes
โ stringToURL
โ uriComponent
โ stringToNumber
โ stringToInt
โ stringToBigInt
โ numberToBigInt
โ isoDatetimeToDate
โ epochSecondsToDate
โ epochMillisToDate
โ jsonCodec
โ utf8ToBytes
โ bytesToUtf8
โ base64ToBytes
โ base64urlToBytes
โ hexToBytes
โ stringToURL
โ uriComponent
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
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 | Zod
Bidirectional transformations with encode and decode
zod.dev
August 26, 2025 at 12:44 AM
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
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)
August 26, 2025 at 12:44 AM
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.
August 26, 2025 at 12:44 AM
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
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
August 26, 2025 at 12:44 AM
"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
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