tltl
is there a definitive solution to the slow language server/compilation issue?
is there a solution where each individual trpc mutation/query is it's own router? and then I just import and use the appropriate "router" when needed. would that help?
I have no need for any of the query invalidation, caching, or nesting "paths", I'm basically just looking to import and run functions on the frontend.
8 replies
is there a definitive solution to the slow language server/compilation issue?
I run into many errors trying to use xtrpc
I also see this caveat in the readme
𝕏tRPC may not work properly if your procedure outputs are not explicitly declared. For best results, add .output to all of your procedures (which is a good practice to not leak sensitive info anyways) and enable explicitOutputs in your xtrpc.config.jsonNot sure if that's related, but we have zero use of
.output in the codebase8 replies