What do you guys think about the approach of importing/exporting tRPC types to be used in separate B
Hello,
I was looking for a way to share tRPC API between multiple electron apps, I thought first about using a
Nx monorepo
but it turned out it's almost impossible to make it work with electron app that use electron-vite
.
After more research I found this repo: https://github.com/mkosir/trpc-api-boilerplate
What I understood from this approach is you export the types of the tRPC server with all db types from the backend repo and you import them in any other -frontend- repo using GitHub API (Octokit).
Is this approach common in general programming environments and what do you think about it?
Thanks.GitHub
GitHub - mkosir/trpc-api-boilerplate: ⚒️ Minimal tRPC API boilerpla...
⚒️ Minimal tRPC API boilerplate for separate BE-FE repositories. Easily publish fully typesafe APIs that any frontend can consume. - mkosir/trpc-api-boilerplate
4.8KMembers
View on DiscordMore Posts
How to add fallback link to tRPC link (Mirror API URL if main URL failed)My API URL is not functioning in Iran, I'm using Vercel and Vercel has banned Iran,
I want to providHow can I show real-time post's replies/comments after a successful a reply mutation?After submitting a successful reply mutation, I want to show a real-time UI update on my frontend?Quick question: how to get mutation body in a middleware, which is for a global logging?Hi everyone!Quick question:
The pic shows that the output of "input" is undefined. Is there any anotError with v11 when using batchingI'm using the lastest version of v11. When I use the batch link I get an trpc inernal error when bat