Malmรถ, Sweden
- Tweets 8,650
- Following 1,877
- Followers 29,246
- Likes 20,685
& thanks to @ballingt for letting me crash in his flat all week โฅ๏ธ
7
1,023
Alex / KATT ๐ฑ retweeted
@trpcio as a data access layer has been awesome as we scale the new PayPal checkout repo. It would have been much messier and less idiomatic to invent our own patterns and thus harder to scale to 90+ devs so quickly, and it allowed us to hedge against server action growing pains
3
17
2,680
Alex / KATT ๐ฑ retweeted
Can the Open Source Pledge actually fix open source? New video just went live talking all about it
2
9
92
16,978
TanStack Query already supports streams! (if you use it with @trpcio) :)
trpc.io/docs/client/react/usโฆ
1
30
3,761
I'll be in SF for a week from next Friday! Who should I meet? โ๏ธ
Anyone who wants to have an office buddy for a day and/or have a sofa that hasn't been slept on for way too long? ๐
9
12
3,768
I'm still trying to understand, could someone please explain how prevState is needed as a React-primitive to solve this problem nicely?
To me this could be solved app-side by:
A) a hidden input with the state at the point of clicking the submit-button (should allow same behavior as prevState?)
B) preventing double submits on forms in onSubmit or by disabling the submit-button, potentially with a idempotency key as a hidden input if I wanted to be fancy
I haven't experienced the problem being solved here at the scale of Facebook so maybe I've been solving it wrongly all my life?
I've yet to see an example that makes this click for me
1
1
12
3,593
to me, anything you'd use it for is better done by a hidden input, see
- ๐ซฃ AFAICT, you can't trust the value here and it needs to be validated alongside `formData`
- ๐ It needs to be the same type as the return type of the action, which makes inference circular
- ๐ฉ the React docs need a troubleshooting section to explain it's there (react.dev/reference/react-doโฆ), it should be a red flag that the API could be tweaked
- ๐งฉ The arguments change depending on how you call it. This sorta goes against the "React way of thinking" that things are an independent "lego piece" that you can drop anywhere
- ๐ The state in `useFormState(action, initialState)` gets serialized and passed between server<->client which to me just adds unnecessary payload
- โน๏ธ If you need to pass additional context with form data, you can add a `<input type="hidden" />`, I don't see why React needs to provide this
3
2,603
Alex / KATT ๐ฑ retweeted
Whatโs new in @tan_stack React Query v5.59.0 youโre asking?
๐ experimental support for use() in React ๐
const { promise } = useQuery(...)
const data = use(promise)
- can be used conditionally
- integrated with React 19 and suspense
- creates and caches a stable promise that resolves when data comes in or rejects
github.com/TanStack/query/reโฆ
Give your thanks to @alexdotjs for contributing this.
Just note that the feature is experimental, and you need to opt in by setting `experimental_prefetchInRender: true` on either your query or globally.
Please try it out and give feedback ๐
10
39
492
60,109
Alex / KATT ๐ฑ retweeted
I built an app that will fork a GitHub repo for you, and push commits directly to your fork replacing text to rename it in every file. No more laborious find and replace just to get into the next YC batch: forkme.mmkal.com
118
168
4,147
256,241
This *almost* worked ๐ appreciate @ryanmagoon for looking into it ๐
2
13
4,186
hey @vercel, I couldn't come last year when I was offered a ticket from y'all, is the offer still open for this year? ๐
Would save me a bit on a trip that will already cost a bunch
3
8
1,305
Middlewares in tRPC ๐
Base procedures
Most apps should only have a few base procedures that cover 99% of the app's use cases -
In the below example, I have:
1. A public base procedure with logging
2. An authed base procedure that extends ^
3. An organization procedure that extends ^
Playground example ๐: tsplay.dev/mA6KQW
See the router definition at the end, but some notable things below (you can open the link and step through the `^?`-comments)
- The procedure builders can be chained which enables code reuse and makes it easy to do eg an `authedProcedure`
you can add multiple `.input()`s in the same chain which enables "half-way" checks in the pipe (see orgProcedure('post.create'))
- You can use the result of `next()` in a middleware which e.g. enables logging of the duration etc
- Any middleware can override properties on the `ctx`
- The .query() / .mutation() finalizes the builder and returns a clean query or mutation (hover `appRouter.addPost` at the very end)
- .input() / .output() supports a wide set of different parsers automatically (zod, arktype, typeschema, etc)
Standalone / `.concat()` middlewares
Both of the above mainly exist with libraries in mind.
`.concat()` merges to procedure builders as long as they're compatible
We deprecated standalone middlewares in favor of `.concat()` as we think it covers all intents of purposes of standalone middlewares
4
55
6,863
How cursed would it be to allow plugins of a library through by encouraging people to use `declare module`-style overrides?
Playing with the idea to break out parts of trpc's procedure builder / middleware thing to its own package, but it's hard to make extendable w/o it
5
7
3,729