Why use unstable_httpBatchStreamLink in React server components?

When using create-t3-app I noticed that they were using

unstable_httpBatchStreamLink

unstable_httpBatchStreamLink

in their

TRPCProxyClient

TRPCProxyClient

when using RSC. I find this strange, since you already have access to the actual

appRouter

appRouter

, doing an HTTP request to your own server adds a lot of overhead. Why use

TRPCProxyClient

TRPCProxyClient

with

unstable_httpBatchStreamLink

unstable_httpBatchStreamLink

and why not just use

createCaller

createCaller

?

I understand why it's done when rendering

'use client'

'use client'

components on the server, because you don't want server code bundled into the client code. But I fail to understand why they opted to also use this method when rendering server components.

tRPC•3y ago•

3 replies

BeBoRE

Why use unstable_httpBatchStreamLink in React server components?

When using create-t3-app I noticed that they were using

unstable_httpBatchStreamLink

unstable_httpBatchStreamLink

in their

TRPCProxyClient

TRPCProxyClient

when using RSC. I find this strange, since you already have access to the actual

appRouter

appRouter

, doing an HTTP request to your own server adds a lot of overhead. Why use

TRPCProxyClient

TRPCProxyClient

with

unstable_httpBatchStreamLink

unstable_httpBatchStreamLink

and why not just use

createCaller

createCaller

?

I understand why it's done when rendering

'use client'

'use client'

components on the server, because you don't want server code bundled into the client code. But I fail to understand why they opted to also use this method when rendering server components.

Why use unstable_httpBatchStreamLink in React server components?

Similar Threads

Why use unstable_httpBatchStreamLink in React server components?

Similar Threads

Similar Threads

Similar Threads