π’ArkType 2.2 is here.
This is a big one, and it's long overdue.
Validated functions, type-safe regex, bidirectional JSON Schema, and universal schema interop.
Here's what's new π§΅
π’ArkType 2.2 is here.
This is a big one, and it's long overdue.
Validated functions, type-safe regex, bidirectional JSON Schema, and universal schema interop.
Here's what's new π§΅
all you need to "learn" ArkType syntax:
1οΈβ£ start with a typescript keyword
2οΈβ£ .autocomplete to discover constraints
3οΈβ£ compose if needed with &, |, etc.
tools are just introspectable functions...
what if you could define them like this?π€
wish TS had rust-style pattern matching?
(it already does)πͺ
π¨Standard JSON Schema v1 just droppedπ¨
π’libraries can now accept ArkType wherever they need JSON Schema
π’100% type-safe with inference built-in
π’day one support from AI SDK
π’TanStack AI and MCP SDK support imminent
Next steps:
β‘οΈshare the announcement
β‘οΈopen issues on projects that can use it
β‘οΈread the announcement
standardschema.dev/json-schema
Standard JSON Schema is already being adopted by AI SDK, Tanstack AI, and MCP SDK.
Shout out to @lgrammel.bsky.social for day 1 support and this clean example featuring @arktype.io π
πAnnouncing Standard JSON Schemaπ
The next spec in the Standard Schema family is here to bring library-agnostic JSON Schema to TS.
Let's make sure everyone sees itπ
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
mission accomplished @mattpocock.com
the typescript ecosystem *desperately* needs type performance tooling.
it's not an overstatement to say this is one of the biggest leaps in that area in the history of the languageπ
We couldn't be more excited to get it in your hands.
Read more/join the waitlist for early access: pullfrog.com
Just tag Pullfrog or setup auto-triggers to...
πΈplan, review, or implement PRs
πΈhandle chores like issue triage and labeling
πΈaddress feedback and CI failures on its own PRs
and it just gets better as your agents do.
Pullfrog is the solution.
It's a unified entrypoint to the agent of your choice in GitHub, with triggers that work consistently as the ecosystem evolves.
With agents becoming more and more capable, GitHub is a natural lower bound for friction.
Some agents provide their own GitHub actions, but the result is a half-baked, fragmented DX that ends up feeling bad for everyone involved.
Earlier this year, @colinhacks.com and I teamed up to create a more open TypeScript ecosystem with Standard Schema.
We couldn't get enough of each other so we're partnering to do the same for agents on GitHub.
sounds fake but I'm starting a company with my nemesis Colin P. Zod
and our first hire is @AndaristRake
and our first product is now in beta
damn too many branchesπ
95% of ArkType syntax is just TypeScript.
The other 5% are extensions like this that are...
β
composable
β
consistent across data types
β
100% safe with helpful type-level error messages
once you go type("string") you never go z.back()
iyky (you don't)
In the next version of ArkType, any Standard Schema is a valid definition.
Zod migration is about to get a whole lot easierπ
fastest, cleanest tuple validation around
RIP z.shark()
long live sharktype
ππ
use a wrapper
<3 thanks for the support as always.
we'll get there! big stuff in the works π§βπ³
agonized for a long time on syntax to return a regex's capture groups rather than just validating the input string...
what do you think?
πarkregex just hit 100k installs/weekπ
if you're still using untyped RegExp() you may as well just write raw .js
string validation has never been this easy
arktypeπ€arkregex