not sure if it ticks all the points, but I'm happily using PandaCSS.

You should trying it.

Btw I want to try ts-go myself on an TS repo, @tkdodo.eu how much is breaking?

dunno, maybe ts-go has different limits?

if I recall, it happens with tsc also, @dogpawhat.tech is right

I got bitten by that, all composition props like "asChild", "as" or the "render" prop from ariakit.org/guide/compos... potentially soffer from this.

At least writing good, accessible integration tests you can catch those a bit more.

I'm recently tinkering on the topic myself, and why not a render prop pattern?

Let's just vibe code a new engine

maybe we just need to learn better how to guide Claude, but personally, it stress me out a bit every time I do an attempt like this

nice article, but made me think that we are not ready enough for vibe coding, all these errors, cannot avoid thinking of that an old research on github issues and some human thinking would have wasted less energy and solved the problem earlier (yes I know the point of the article!)

Oh ok so potentially the ref gets refreshed too often, but I guess the latest render its not discarded, I'm wondering if it's still better to use a useLayoutEffect in this case

to my eyes updating the ref on render its ok, because its just an assignment operation done on a the ref value so I don't think anything else is needed.

I've done a PoC with the sentry useHotKeys hook and using my useLiveRef hook copied from @ariakit.org (github.com/ariakit/aria...)

It works but then I discovered that the original code from ariakit uses a useLayoutEffect, now I'm curious if I'm actually doing something harmful

Mmm I Remember to have done this in a case, I'll check it later

Why not just update the ref directly on render? Instead of taking advantage of a useEffect?

Extra files does not mean extra workers spawned by vitest?

ariakit.org, ark-ui.com

I'm sure that I just need more practise on that, the project where I tried it is also custom and a bit convoluted, with client / backend folder, api docs folder, tests, stories files, mocking system, etc. etc.

I tried knip recently feels like I need to take a certification only for the config 😆

just use something like panda-css.com and enable typesafety

You have taken some Gorgonzola, nice move!

yeah agreed, I think it may be useful only for the development mode related mocks

this would be extremely cool! I've tried to do it previously in my codebases, but it always ended up a little mess

If I understand correctly, what you need is a mapped type in combination of a generic function type: www.typescriptlang.org/play/#code/G...

One of the reasons I started developing Waku waku.gg is to experiment with Jotai and RSC. I'm proud of the first PoC of Waku/Jotai integration. It's still very limited, and we need to explore more, but for me, it's a great milestone.

Demo: stackblitz.com/edit/github-...

Standard Schema A common interface for TypeScript validation libraries

BIG DAY 😇

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

It's sad that the proposal seems stuck 😢

<Button type="button" as={<a href="/" />}> Click me </Button>

like that:

We use the render prop pattern inspired from @ariakit.org to render the button as links and viceversa

Just wow 😮