Christopher Ehrlich

> @c-ehrlich Hi, your example is for the pages dir is with the `createNextApiHandler` but I am currently using: > > pages dir + `fetchRequestHandler`. > > Can I just...

We've added an example for the current versions of App Router + tRPC using `concat`. Standard middleware works as well, but is a bit less composable. Either is fine :)...

closing for now, but please ping me if something still isn't working.

tldr: I see the problem with not allowing anything but `query` and `mutation`. Not a fan of overloading procedures. ### flushOutput When thinking in normal http, `flushOutput` feels like a...

Just saw that you opened this. I've been working on some ideas for restructuring the docs as well - talked about tRPC with a lot of people at a conference...

The first sentence of the current context page is "Your context holds data that all of your tRPC procedures will have access to, and is a great place to put...

What's wrong with something like: ```ts import { someServiceSingleton } from "../util/some-service"; export const createTRPCContext = () => { return { someService: someServiceSingleton }; }; ``` this will not be...

(we have a fix for this releasing soon in `@axiomhq/js` as we didn't really have a good reason to use `global` in first place, but there's probably many other libraries...

i've been meaning to work on this but haven't had the time. would be amazing if you want to pick it up! maybe pages/app can be a toggle or some...

i will try the `added` event solution tomorrow :) the `invalidated` event is something that i patched into the QueryClient, see: https://github.com/c-ehrlich/broadcast-invalidation-demo/commit/e2133b9bb01876d31d9b259933b212002becd705#diff-b432175c3da3a30468adb42601d364ab07e49f55f25a72d0da521a87cb968423R28 (obviously not the correct implementation, just a demo)...