
waterfalls: gorgeous in iceland, terrible in your network tab new in tRPC: query handles trpc.io/docs/client/tanstack…

Move Fast and Break Nothing. E2E typesafe APIs without schemas nor build steps. 🌟 35,000+ 💬 trpc.io/discord 🤓 github.com/trpc/trpc

waterfalls: gorgeous in iceland, terrible in your network tab new in tRPC: query handles trpc.io/docs/client/tanstack…


After a brief hiatus while npm fixed their WAF... tRPC v11.22 is out, now with typesafe procedure errors! Using this API, @trpc/openapi will also emit accurate error responses

Since September, we have been unable to publish because every URL under `PUT registry.npmjs.org/@trpc/` is being blocked by a @npmjs @Cloudflare WAF. You can even prove it locally, they've just wholesale blocked our npm scope. Support have not yet done anything to help.
anyone from @npmjs that can have a look at request #4870687 from me? nick tried first but got a non-response


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

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


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

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’s here!
Agent skills with @tan_stack Intent Now in tRPC

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

