David Blass

What do you care most about for your TS schemas? 👀 - Smallest bundle - Fastest startup - Fastest validation Reply with yours

tsassembly when

it ts7 already legacy?😭

📢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

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🙇

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

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

problem: your RegExp is beyond human comprehension solution: pnpm i arkregex

I'll take "meticulously typed regex features you probably didn't know existed" for $500

in the latest version of arktype: regex properties and index signatures from arkregex🔒

imagine using untyped regex in 2025

arkregex is ridiculously optimized. even expressions like this are inferred instantly. but what about the most extreme cases?🧵

new RegExp(): ❌types 😴tired arkregex: ✅types 🫨wired

I am looking for a full-time job. Being independent in open source for 3.5+ years has been wonderful. I've gotten done most of the high-level goals I wanted to, and miss having people & structure around me. If you know of a role for a staff-level TypeScript+web developer, let me know! 🙂

hopefully this is not too insensitive

my abusive relationship with typescript's type system continues

📢Introducing ArkRegex📢 a drop in replacement for new RegExp() with types ⬇️

new to typescript? here's a handy little type for parsing regular expressions:

soon

🙅convoluted regex 👍simple types

days of remaining sanity also numbered btw

Ever get mixed up about unions and intersections? ArkType has your back🫡

"any sufficiently advanced typescript types are indistinguishable from magic" - Arthur C. Clark, 1962

Like type-safe environment variables? Now there's a better way to get them with arkenv⛵❤️