How will TRPC adapt to an IsolatedDeclarations world

[apjoseph]

Typescript 5.5 added IsolatedDeclarations which promises to end both the hell related to sharing .d.ts files between modules as well as end the constant typescript language server often experienced with typescript codebases.

IsolatedDeclarations requires that types be explicitly declared rather than inferred -which seems fundamentally incompatible with TRPC's design which relies heavily on type inference.

The creation of this feature seems to be a signal to typescript users from the typescript devs that if we want decently fast compilation speed and to be able to avoid constant language server lag in our IDE's, we will have to eliminate all "slow types" in our codebases.

Given the performance benefit, I would expect that this setting will quickly become ubiquitous.

I am therefore wondering how/if TRPC plans to support development with IsolatedDeclarations, or if not what we can do to reduce the issues caused by "slow types".

I have only been aware of isolatedDeclarations for two days, and I have not yet determined whether it is just hype or the "gamechanger" it is being described as.

Nevertheless, I am curious to get the community's take both because my organization is using TRPC and because if anyone has first hand experience with "slow types", it would be TRPC users with monorepos full of gigantic router definitions.