👋 I'm Alex & I tweet about web dev stuff Creator of @trpcio, work @square, scout @a16z

Malmö, Sweden
I want to say that an array satisfies an array of type X. What I'm missing here to get the behavior of `as const` + `satisfies X`? typescriptlang.org/play?noUn…
13
3
82
57,076
Alex / KATT 🐱 retweeted
🍿 @alexdotjs going on stage in a few minutes to show how to Move Fast And Break Nothing with @trpcio here at @NodeCongress
1
3
14
2,252
Alex / KATT 🐱 retweeted
Congrats @alexdotjs and all @trpcio contributors for making it into the first cohort of the GitHub Accelerator. Well deserved 🚀🎉
Announcing the inaugural cohort of the GitHub Accelerator: 20 projects embarking on a 10-week journey to build a sustainable funding model. github.blog/2023-04-12-githu…
5
76
17,475
Alex / KATT 🐱 retweeted
Announcing the inaugural cohort of the GitHub Accelerator: 20 projects embarking on a 10-week journey to build a sustainable funding model. github.blog/2023-04-12-githu…
21
78
481
440,665
Alex / KATT 🐱 retweeted
Alternatively, use tRPC and never think about query keys again
Problem: With react-query, we may declare inconsistent query keys. That leads to cache misses and duplicated cache entries. 👎 Solution: 1. Wrap each useQuery call in a custom hook. Store the hooks in /hooks. 2. Put the fetch call in the custom hook. *Don’t export it*. 3. Forbid calling useQuery outside /hooks via ESLint’s no-restricted-imports. Forbid calling fetch outside /hooks too. This assures the hook is the only way to query. 👍
8
10
175
53,683
Alex / KATT 🐱 retweeted
Separation of concerns? I’m concerned by how often we separate things
27
22
360
126,663
Alex / KATT 🐱 retweeted
Working hard as diligently ever to make sure you check out @trpcio and promoting a healthier relationship with @typescript, it's @alexdotjs! @cityjsconf Bonus pics in the reply.
1
3
11
2,716
Alex / KATT 🐱 retweeted
This guy rocks 🤘
4
4
82
19,386
Alex / KATT 🐱 retweeted
Just your average Thursday
6
5
31
7,051
Yesssss, I always vendor a fn called `promiseProps()` to do this I wish it was `Promise.props({})` but I can def live with `.ownProperties`
ECMAScript excitement 😉 Congrats to my coworker @acutmore @TechAtBloomberg on advancing the Await Dictionary proposal to Stage 1 @TC39 🎉 Promise.all returns positional results as an array. This proposal will allow named results inside an object 👍
2
19
5,855
Alex / KATT 🐱 retweeted
In React Labs posts, we write about projects in active research and development. Since our last update, we’ve made significant progress on our long-term projects, and we’d like to share what we’ve learned. react.dev/blog/2023/03/22/re…
14
130
717
334,308
I actually prefer the UX of the ones without streaming here since they're all so fast that the loading state mainly feels distracting Can streaming be deferred to be used only if it exceeds a certain millisecond threshold?
Fun fact: I wrote the first version of this demo I enjoyed learning Remix and understanding its design tradeoffs more deeply. 💿 remix-on-the-edge.vercel.app
3
34
27,000
`<Suspense threshold={200}>...<Suspense>` Is/will this be possible? Is it a bad idea? ELI5
6
20
4,272
*awaiting @RyanCarniato to show up & share how this is already solved in solid or marko*
2
28
2,159
Yoooo, next week I'm going to speak at @cityjsconf in London! Grab a ticket and come hangout! 🏴󠁧󠁢󠁥󠁮󠁧󠁿
6
1
23
3,338
if something were to happen to me, @trpcio will be in safe hands
7
178
15,670
seems like tagging ppl in photos is broken that's @s4chinraja y'all - he's great
1
28
2,459
(For the record - I'm in good health apart from some herniated discs in my back that occasionally fucks with me up)
1
19
2,106