Alex / KATT

pong

+1

Ohhh I seee, I have too many example projects 😂 if you ever want a reference, this is to go to: https://github.com/trpc/examples-next-prisma-starter

I managed do get `4xx` working by letting the user "slip through" the auth handler, which doesn't feel great, but it works -- If the connect-handler returns 401 it actually...

You gotta do it 1 full router at a time unfortunately. Edit: But you can create a new router and move one proc at time

@sachinraja WDYT? It would also help validate that we don't break ESM support etc

Let's give it some time to marinate and for other people to chime in. I know @TheoBr would like it

I'm happy to move everything to a `trpc` prop for `next`. For v10, this can be a breaking change - my guess is that those properties are probably only used...

What @iway1 is describing could be circumvented by: - Splitting the queries into different components - Adding support for `useQueries()`

Yeah yeah, @waptik, that's intended, I have it to enable "view source" functionality on e.g. https://kitchen-sink.trpc.io/react-hook-form Comes from https://github.com/trpc/trpc/blob/main/examples/kitchen-sink/src/server/routers/source.ts