🔮 OSS Fellow @ Clerk
🦆 Friendly neighborhood TypeScript nerd
🧑🏼💻 Prev @ Bun, EdgeDB, YC, MIT
z.codec() is a new API for defining *bi-directional transformations* in Zod
z.codec() is a new API for defining *bi-directional transformations* in Zod
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! 🤘
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! 🤘
lu.ma/waqmeggb
lu.ma/waqmeggb
💎 7x faster object parsing
💎 20x reduction in tsc instantiations
💎 57% smaller core bundle size
💎 metadata via .meta()
💎 z.toJSONSchema()
💎 z.templateLiteral()
💎 z.stringbool()
💎 z.int32(), z.float32(), etc
💎 z.file()
💎 new logo 😇
💎 7x faster object parsing
💎 20x reduction in tsc instantiations
💎 57% smaller core bundle size
💎 metadata via .meta()
💎 z.toJSONSchema()
💎 z.templateLiteral()
💎 z.stringbool()
💎 z.int32(), z.float32(), etc
💎 z.file()
💎 new logo 😇
✓ features are week-to-week (~140k impressions)
✓ simple auction-based pricing (per-week or standing bids accepted)
✓ artwork subject to approval
DM/email me if your company is interested! 🤙
✓ features are week-to-week (~140k impressions)
✓ simple auction-based pricing (per-week or standing bids accepted)
✓ artwork subject to approval
DM/email me if your company is interested! 🤙
Introducing Standard Schema! It’s a specification for a standard interface to be implemented by TypeScript schema libraries. The goal is to make it easier for frameworks and tools to accept user-defined schemas, without writing separate adapters for different libraries.
standardschema.dev
Introducing Standard Schema! It’s a specification for a standard interface to be implemented by TypeScript schema libraries. The goal is to make it easier for frameworks and tools to accept user-defined schemas, without writing separate adapters for different libraries.
standardschema.dev
her response changed my life
her response changed my life
finally i can structure things internally however I want w/o cluttering autocomplete for end users
cc @colinhacks.com @ssalbdivad.dev @effect-ts.bsky.social
github.com/microsoft/Ty...
finally i can structure things internally however I want w/o cluttering autocomplete for end users
cc @colinhacks.com @ssalbdivad.dev @effect-ts.bsky.social
github.com/microsoft/Ty...
cc @colinhacks.com @ssalbdivad.dev @effect-ts.bsky.social
github.com/microsoft/Ty...
- lazily computes a value when accessed
- autocaches the result
- typesafe
i use this all the time...unlike a naive getter there's no runtime overhead after the first invokation since the getter itself is overwritten with the memoized value
- lazily computes a value when accessed
- autocaches the result
- typesafe
i use this all the time...unlike a naive getter there's no runtime overhead after the first invokation since the getter itself is overwritten with the memoized value