tRPC.io 🧙‍♂️

We've just* passed 30k stars on @github!! 🤩

How is @trpcio `httpBatchLink` able to fold multiple procedure calls into ONE batched call? Like how does `Promise.all([a.query(), b.query()])` end up in only a single HTTP request It's a pure timing trick built with a simple dataloader: Every call you make in the same tick gets pushed into one shared buffer. Only the very first call schedules a `setTimeout(dispatch)` Because `setTimeout` is a macrotask, it only runs after your synchronous code finishes. So by the time `dispatch` fires, all the calls from that tick are sitting in the buffer together `dispatch` then joins them into one request (`a,b,c`), sends it, and resolves each call's individual promise from the response array The neat part: `Promise.all` isn't special. Anything called in the same tick batches. The only thing that breaks it is an `await` in between, which yields to the event loop and flushes early I think this is a really elegant design: using the language's semantics for batching instead of exposing an explicit API

@iamthatcris @ts_rest Both REST and tRPC are just HTTP+JSON with a fancy sticker on 🙂

Why is @ts_rest a dead library? Its value proposition is similar to @trpcio, and REST is way more popular than RPC.

On the side I'm setting up fumadocs (by @fuma_nama) by piping @colinhacks's @trpcio routers through `trpc/openapi` (alpha) to get well designed auto-generating docs. Some rough edges but working well so far.

remember trpc? we passed 40k stars the other day

🥳

@villiamstrandh @EffectTS_ You could probably take opts.path instead of passing the path manually Looks great!

Made a tiny @trpcio helper for running @EffectTS_ code and it feels really nice. Keeps procedures super clean and moves the real logic into services.

@rickyfm So you’re shipping it today, right?

I was going to ship a blog post today titled "We're deprecating useEffect" but the more I wrote it the less it sounded like a joke

@jullerino Now I don’t have favourites, but… Nick

Nick carrying @trpcio lately 🙌🙌🙌 Give the man some support

tRPC OpenAPI support isn't just about generating clients. You can use @oasdiff on your own API to check for breaking changes or generate changelogs too

@nstlopez @NckLcs

@NckLcs Nice

And it's out, tRPC 11.16.0 comes with updated OpenAPI support to support cyclic types, and lazy zod schemas!

Planning to drop an update to @trpcio OpenAPI support this weekend Removing the type depth limit and adding support for cyclic types, which was an initial limitation of the alpha

It only makes sense that if you use the GStack, you should pair it with TanStack too.

@NckLcs Please, no more types

Sorry @trpcio this small feature's getting out of hand

@trevorlasn @tan_stack We just released an (alpha) OpenAPI schema generator which should help interoperability with codegen tools, otherwise the vanilla client is a great choice to create some tools and you can use a local localLink and/or the create caller system to bind procedures in the backend

@trpcio @tan_stack tRPC + agents feels like a natural pairing. curious what the DX looks like for defining agent tools from existing procedures. been using react query for server state and the type safety is already addictive.

Agent skills with @tan_stack Intent Now in tRPC

@theo @jullerino Are you going to let your employee undermine team Theo like this?

@jullerino @trpcio I’m crying oh my god

Always amazed by the people who dm me in support of the anti-Anthropic stuff. Feels like half the industry is scared to poke the bear. Thankful I am in a position to fight back on the bullshit. Will do my best. Sorry in advance if we get Claude banned on T3 Chat 🙃

It’s here! x.com/trpcio/status/…

You’ve all been thinking it, and it’s coming

@ThePrimeagen I never understood webp

why does everyone hate webp?

Do submit issues and corrections! This is a near doubling of our documentation surface, only made possible by AI, and impossible to deeply critique as a whole. It will very likely have problems to iron out