orpc-max-length-problem

Resolve the oRPC maximum length problem by disabling `"declaration": true` in `tsconfig.json`, defining `.output` types for procedures, and exporting the router in parts to reduce the exported object size.

Disabling the `"declaration": true` option in `tsconfig.json` prevents the generation of large declaration files that trigger the oRPC maximum length problem, improving TypeScript inference performance and maintainability.

Export the oRPC router in parts instead of a single large object to reduce the exported object size, mitigating the TypeScript maximum length problem and improving project maintainability.

Yes, defining `.output` types for oRPC procedures improves TypeScript inference and reduces the complexity that contributes to the maximum length problem in large projects.

The best way to optimize oRPC performance involves adjusting TypeScript configuration by disabling declarations, defining output types, and exporting the router in parts to restructure code and reduce object size.

The oRPC maximum length problem is a TypeScript issue that primarily affects large projects, where the accumulated complexity of types and exported objects exceeds TypeScript's handling capacity and degrades performance.