Victor

Was about to open a similar issue, `getInitialProps` in `_app` goes against Next.js best practices and defaults, this should really explicitly be decided on a page-by-page basis using the standard...

@KATT Thanks for looking into this! I have checked my setup once more and can confirm that I have properly integrated the example 😄 Since I'm able to reproduce this...

@KATT We can of course revert, but right now testing is split into three separate workflow files all essentially doing the same thing - IMO it's a lot cleaner to...

@KATT That's it, the node v18 test is now correctly reproducing the problem with the `next-prisma-starter-websockets` example. The standalone server example seems to work as expected. Might be specific to...

I have injected some dirty JS into the appropriate `node_modules` files to log what's happening. Here's an example fetch (wrapped in a `Promise`) that gets resolved from https://github.com/trpc/trpc/blob/7739c934130bbb2cea2586523b1af552f560a749/packages/client/src/internals/httpRequest.ts : ```...

@KATT I have included a preliminary `stripHeaders` implementation. Judging from the built type declarations, the function can be accessed with a simple `@trpc/client` import (would be easier to evaluate if...

Tests appear to be failing on unchanged files?

@KATT Had to disable an ESLint rule in the `interference.test.ts` file (no involvement): https://github.com/trpc/trpc/blob/f19ede4a67721d882602d75471c12ff506a3857c/packages/server/test/inference.test.ts#L1 The react testing file has a bunch of problems, this was the least I could do...

Everything's working locally for me now, I don't know why some tests are still failing on GH, but it looks like my changes don't have anything to do with it...

@KATT Resolved