Merging api and fe repos in a monorepo

[cloudcompute]

Hi @mkosir

I went through the code of both of your boilerplates and a demo too, looks great (little slow though, probably seeding database took time).

Would you suggest creating a monorepo that comprise both api-boilerplate and fe-boilerplate.. what do I need to take care of while doing this?

Typescript graphql has wonderful authorization / fine-grained permissions libraries. In case of trpc, is there any library that allows great control over permissions including ABAC?

I also had a quick look at the TypeScirpt guide and I found it amazing!

Thanks

[mkosir]

Hi @cloudcompute, glad you like it!
If you think monorepo would be right fit for your use case I suggest to take a look a official trpc website examples, since by default I think majority are monorepos. On the contrary this boilerplate tries to do quite the opposite to have server and client app in separate repos.

Typescript graphql has wonderful authorization / fine-grained permissions libraries. In case of trpc, is there any library that allows great control over permissions including ABAC?

Good point, but didn't yet had the use case for fine grain permission control/ABAC with trpc, but for sure permission architecture with trpc is something to think about!

I also had a quick look at the TypeScirpt guide and I found it amazing!

Nice to hear you find it useful!

[cloudcompute]

I had worked on the monorepos earlier. All I wanted to ask was that. would it take time to merge the client and server repos of yours, for example, I am seeing, you are using 'octokit' library in the FE code. I don't think there is any need for it, in case of monorepo.

[mkosir]

I see, yes in the case in monorepo octokit would be completely redundant.

[cloudcompute]

Also, if we use a monorepo, Zod validations and other project-specific types can be shared by both FE and BEs.