tRPC.io 🧙‍♂️

Move Fast and Break Nothing.
E2E typesafe APIs without schemas nor build steps.
🌟 35,000+
💬

[tRPC.io 🧙‍♂️ @trpcio]

waterfalls: gorgeous in iceland, terrible in your network tab

new in tRPC: query handles

https://t.co/EjIN4F9hps

[tRPC.io 🧙‍♂️ @trpcio]

@kajtszy 🙀
👀👀👀

[tRPC.io 🧙‍♂️ @trpcio]

Our website has gotten a bit of a refresh 🎨
https://t.co/9VlXvVyepO

[tRPC.io 🧙‍♂️ @trpcio]

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

[tRPC.io 🧙‍♂️ @trpcio]

@jullerino Finally, a level playing field

[tRPC.io 🧙‍♂️ @trpcio]

@brophdawg11 @npmjs @Cloudflare Thanks for the tip, good to know it could be a readme. Looks like a different cause for us though, between the last successful publish and the first failure, readmes didn't change, not much changed even in code 😣

How did you guys figure it out? Any contacts/support involved?

[tRPC.io 🧙‍♂️ @trpcio]

Since September, we have been unable to publish because every URL under `PUT https://t.co/LCQI7jouwM` 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.

[Alex / KATT 🐱 @alexdotjs]

anyone from @npmjs that can have a look at request #4870687 from me?
nick tried first but got a non-response

[tRPC.io 🧙‍♂️ @trpcio]

@alexdotjs @tan_stack NPM will probably even let you publish 😭

[Nick @NckLcs]

tRPC can’t publish new package versions for at least a week now, and it looks like an @npmjs Cloudflare WAF is blocking our @github actions from publishing on a vanilla GitHub runner

Anyone out there who can help?

[tRPC.io 🧙‍♂️ @trpcio]

@hiitsricardo Still alive!

[Chris Cook @zirkelc]

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

[tRPC.io 🧙‍♂️ @trpcio]

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

[Brennan McEachran 👨‍🚀 @i_am_brennan]

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.

[Alex / KATT 🐱 @alexdotjs]

remember trpc? we passed 40k stars the other day

[tRPC.io 🧙‍♂️ @trpcio]

🥳

[tRPC.io 🧙‍♂️ @trpcio]

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

Looks great!

[tRPC.io 🧙‍♂️ @trpcio]

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

[tRPC.io 🧙‍♂️ @trpcio]

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

[tRPC.io 🧙‍♂️ @trpcio]

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

[tRPC.io 🧙‍♂️ @trpcio]

@nstlopez @NckLcs