tRPC without SSR
getInitialProps
, which has kinda of a cool effect in terms how a page is rendered, since it's rendered server-side on initial requests and client-side on route transitions.
Unfortunately, enabling ssr means that you can no longer use getServerSideProps
(which I know is only fixable by next.js and not tRPC). But how to replicate the getInitialProps
behaviour then?
Let's say I'm building a blog; due to SEO it's basically necessary to render my posts server-side. But when navigating through the site loading posts on the fly would be totally fine. How to do that without ssr
?...trpc + expo react native issue

Can you chain middlewares in v10?
Load data client-side via react-query while using tRPC with SSR
Serving clients in another repository?
How to access hooks while initializating react query client for nextJS?
queryCache
to handle errors or display toastr
, etc.
The way trpc initialize the react query client with nextJS using the createTRPCNext
doesn't give the option to access/call any hooks.
There is any other way to initialize trpc on NextJS that happens in the react component lifecycle as it would happen if we'are using only react query?...
How to execute mutation outside of react context?
window
in _app.tsx
```...When not to use tRPC?
Bi directional infinite query example with prisma
hasPreviousPages
gets blown away when I go to the next page. Anyone have an idea what might be happening?Websockets not sending data

Query keys
Possible to use tRPC proxy client inside Edge Runtime?
Is inferRouterInputs & inferRouterOutputs exported from trpc-server?

v10 migration using codemod
NextJS 13 compability.
SSR and loading indicators - I don't get it
utils/trcp.ts
sets ssr: true
, but the pages/index.tsx
example uses
```
const hello = trpc.hello.useQuery({ text: 'client' });
if (!hello.data) {...Prefetch forEach
Making input to trpc route from Prisma generated type
NextJs middleware broken by tRPC
/api/trpc
call and there is no session it tries to redirect to the login page breaking the redirect and trpc itself. Is there a way to get this working so redirect would actually work as expected?
How to infer the output of a mutation? The current methods appear to be depreciated.
