Migrating pages router to app router
hey there. long time user, first time caller. I'm trying to migrate my pages router nextjs app to next app router. I'm struggling to understand some core trpc + ssr principles I think.
afaik, my pages router pages were rendered server side if possible, and all useQueries came preloaded with data on render. Now I'm following along the docs here and really struggling to make things work that way.
It seems I need to manually specify what components are server and which are client side. Let's start with my landing page. it has hooks like usePathname, useSearchParams, so I don't think I'm able to make the page be a server component. Hooks aren't allowed there. I'm also wrapping all my pages in a layout which includes a sidebar that highlights the active link, all of this sounds to me like I can't use it server side. I also use an animated component that uses useEffect and useState, again, no server component afaik.
...
Troubleshooting createTRPCOptionsProxy with Server Components and Context Passing
How does
createTRPCOptionsProxy work in server components?
I'm creating a context that passes the hono context to createTRPCContext in order to obtain the HTTP headers, since I need to forward those headers to the better-auth API to get the session I use @hono/trpc-server which created by the hono so I can use hono as adapter of trpc.
```...
httpStreaming with NonJsonSerializable
i have a question lets say i have this
link setup to make httpStreaming work and also make NonJsonSerializable stuff work (formdata)
if in the mutation i return json it works perfectly but if i return an stream i get Cannot use stream-like response in non-streaming request which makes sense
but is there any way of making it work?...
makeQueryClient missing default arguments
following documentation, the dehydrate & hydrate arguments are not valid when using makeQueryClient
