NI'm still figuring an understanding of this class of error, but I'm guessing you have prisma installed in the API, but not hoisted to the top of your monorepo? Therefore the client app can't resolve the types properly, even though you're returning prisma types from some procedure(s)
NIf you're using npm/pnpm/yarn workspaces then most dependencies should be hoisted up as parents of all the packages in your repo
NAmazing, it's such a vague error so I'm glad that worked 
N@Kimblis similar issue to yours
KSo if you have this folder structure:
you can install package in the root folder and you don't need to install the same package in the separate server folders? They will know about this package?
package.json
API1 ---
package.json
API2 ----
package.json
you can install package in the root folder and you don't need to install the same package in the separate server folders? They will know about this package?
Kor do you need to do some additional work?
KOh god...
Kthis really worked
K
NIf you set up workspaces in your root package.json then one install command will install the whole repo too
KI haven't set up them, however I don't get errors anymore, so that means that it knows about the packages?
N
KHey @DeusLicht could you explain a bit more since I'm still having some issues? As I believe workspaces are being used only if you deploy everything all together? I'm deploying each service in my monorepo separately, so probably workspaces isn't the best choice here? Any ideas how can I share these packages?
Nworkspaces are for managing a monorepo, nothing to do with deploying all together
NYou can keep your deploy scripts and stuff in the individual package.json files
KOkey, maybe one of you will be able to help me a bit, it's my first time working with monorepo structure (project was started by other developer and then he just left, so now I'm cleaning up stuff). So basically we have root folder and inside 3 backend services and 3 frontend services, and 1 shared service for each backend and frontend called
common-backend and common-frontend,right now i'm worried only about backend services. All of them are deployed separatelly. I added shared packages to my root folder package.json and added all 3 backend services as workspaces. Each of backend service has it's own package.json with individual packages. If I view my backend service node_modules it looks really empty. Also each service depends only on each other and on common-backend. Before I was using ts aliased paths to reference my common-backend, but since now I started to use workspaces I added it as dependency into package.json and reference it as a regular npm package (is that a good practice?).