feat: transport that does not depend on global fetch

Describe the feature you’d like to request

I’d like to see a transport layer that is pluggable and allows for other implementations to exist and does not assume the existence of fetch in the global (or window) scope.

Describe the solution you’d like to see

A well-defined interface for the transport layer that can be easily swapped out for other implementations.

Desribe alternate solutions

Global patching, described here: https://github.com/trpc/trpc/discussions/1982

Additional information

Related: https://github.com/trpc/trpc/discussions/1982

Node 18 announcement: https://nodejs.org/de/blog/announcements/v18-release-announce/#new-globally-available-browser-compatible-apis

👨‍👧‍👦 Contributing

• 🙋‍♂️ Yes, I’d be down to file a PR implementing this feature!

[KATT]

We should probably do this tbh:

export interface TRPCClientRuntime {
-  fetch: TRPCFetch;
-  AbortController?: typeof AbortController;
-  headers: () => HTTPHeaders | Promise<HTTPHeaders>;
  transformer: DataTransformer;
}

And

export interface HTTPLinkOptions {
  url: string;
+  fetch?: TRPCFetch;
+  AbortController?: typeof AbortController;
+  headers?: () => HTTPHeaders | Promise<HTTPHeaders>;
}

[jlalmes]

Hi @moltar - this is already possible, I think you are describing the purpose of adapters (router-side) and links (client-side). Please see trpc-chrome as an example for web extensions where the message passing transport layer is: chrome.runtime.connect(...).