Multiple prisma clients and databases

[emilbryggare]

Using Prisma with Turborepo works great when following https://turbo.build/repo/docs/handbook/tools/prisma if there is only one Prisma client in the monorepo.

However, when running Turborepo with multiple Prisma clients and databases they will overwrite each other. It is OK if you only use one database per app, then you would just have to be careful when you run prisma generate so the client is generated for the app you are working on.

But if you have multiple clients/databases in one app things get more difficult. There are loads of hacks out there, some mentioned here prisma/prisma#10433 (comment) but no real solutions as far as I can tell.

I've added a simple reproduction of the use case based on with-prisma example here: emilbryggare#1

Just wanted to raise awareness of this here and maybe it is worth adding a caveat to the docs about this so users are aware. What do you think?

[Neosoulink]

Hi @emilbryggare, did you find out how to solve that?

I have my turbo repo project manages with pnpm and inside of it i do have one package containing a main database, but also inside two apps in the project they have their own Prisma schema.

Yes I'm getting a very very weird behavior when trying to generate codes, because of symlinks pnpm strategy, my generated codes are overwriting each others and I'm not able to use my Prisma logics correctly

[Neosoulink]

Hey @emilbryggare, sorry to come back to you like 3 weeks later 😅

But I solved the problem. I specified the output directory inside all the prisma.schema files inside my turbo-repo project like follow:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = []
  output          = "../node_modules/.prisma/client"
}

💡 Note that the node_modules in the above output directory represent the app/package node_modules

And I changed the default import from @prisma/ to .prisma/

E.g: import { PrismaClient } from ".prisma/client";

[srizvi]

Thanks for the solution @Neosoulink, worked for me.

[adamspotlite]

@Neosoulink did you have any problems with seed scripts for this? getting:

TypeError [ERR_INVALID_MODULE_SPECIFIER]: Invalid module ".prisma/client" is not a valid package name imported from /home/some-project/packages/db/src/index.ts

even tho typescript seems fine...

[Neosoulink]

Hum... Unfortunately, I did not have that problem back then, and all my seeders were working just fine.

Is it possible to share more details (or repo link) for your issue?

It looks like this one is not a problem related to turbo-repo or prisma

[adamspotlite]

i pulled out the seed script into a different package, so that i could import { prisma } from "@acme/first-prisma-package", hacking my way around the issue 😅

Will try to get back around to a repo link in the next couple days 👍

[anthonyshew]

Looks like @Neosoulink's answer is working for folks, judging by emoji reactions!

Hey @emilbryggare, sorry to come back to you like 3 weeks later 😅

But I solved the problem. I specified the output directory inside all the prisma.schema files inside my turbo-repo project like follow:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = []
  output          = "../node_modules/.prisma/client"
}

💡 Note that the node_modules in the above output directory represent the app/package node_modules

And I changed the default import from @prisma/ to .prisma/

E.g: import { PrismaClient } from ".prisma/client";

In the interest of cleaning up our GitHub Discussions, I'll mark this as closed! (I would mark it as answered but the GitHub UI isn't letting me do so.) 😄

[jmunozz]

No public repo.
Basically I used your solution in a turborepo project where I need each app to have its own database with its own schema.
When running npx prisma generate it created a node_modules/.prisma folder with this package.json inside:

{
  "name": ".prisma/client",
  "main": "index.js",
  "types": "index.d.ts",
  "browser": "index-browser.js",
  "sideEffects": false
}

I then built my app. No problem yet.
But when I ran dist/index.js, the error happened.

I am using a specific tsconfig with and ESM module in my package.json.
Following is my tsconfig.json:

{
    "$schema": "https://json.schemastore.org/tsconfig",
    "display": "Default",
    "compilerOptions": {
      "esModuleInterop": true, 
      "module": "NodeNext", 
      "target": "esnext", 
      "sourceMap": true, 
      "strict": true, 
      "composite": false,
      "declaration": true,
      "declarationMap": true,
      "forceConsistentCasingInFileNames": true,
      "inlineSources": false,
      "isolatedModules": true,
      "moduleResolution": "NodeNext",
      "noUnusedLocals": false,
      "noUnusedParameters": false,
      "preserveWatchOutput": true,
      "skipLibCheck": true,
      "strictNullChecks": true
    },
    "exclude": ["node_modules", "__tests__"]
}

I think the probleme came from the fact that I tried to import it as a package.
I managed to fix it by replacing output and import it as a I would do from any other file in my project.

generator client {
    provider = "prisma-client-js"
    output   = "./client"
}

Then in db/client.ts

import { PrismaClient } from "../../prisma/client/index.js";
export * from "../../prisma/client/index.js";

declare global {
  var prisma: PrismaClient | undefined;
}

export const prisma = global.prisma || new PrismaClient();

if (process.env.NODE_ENV !== "production") global.prisma = prisma;

[Neosoulink]

@jmunozz, yes, this is another approach to solving the problem... Even though you lose the packaging logic by doing that

The idea is just to avoid overwriting the Prisma-generated code.

---

Maybe you did that already, but don't forget to add the folder ./client/ in you .gitignore

[adamspotlite]

@jmunozz i had the same thing come about, although originally I didn't. Did you end up staying with this solution?

[ManupaDev]

This works fine locally and even build on Vercel but when i do visit a to a page with a db fetch it fails with the follwoing error

Unhandled Rejection: PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x". We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs. This is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" next to the resulting bundle. Ensure that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied next to the bundle or in "node_modules/.prisma/client". We would appreciate if you could take the time to share some information with us. Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation The following locations have been searched: /var/task/apps/web/node_modules/.prisma/client /var/task/apps/web/.next/server /vercel/path0/apps/web/node_modules/.prisma/client /var/task/apps/web/.prisma/client /tmp/prisma-engines at wa (/var/task/apps/web/.next/server/chunks/5042.js:64:756) at async Object.loadLibrary (/var/task/apps/web/.next/server/chunks/5042.js:111:10016) at async wt.loadEngine (/var/task/apps/web/.next/server/chunks/5042.js:112:448) at async wt.instantiateLibrary (/var/task/apps/web/.next/server/chunks/5042.js:111:12736) { clientVersion: '5.15.1', errorCode: undefined } Node.js process exited with exit status: 128. The logs above can help with debugging the issue.

[jharrell]

@ManupaDev hello! I'm from the Prisma team and we're looking into this.

These problems should be resolved if you use our monorepo plugin (docs available here)

If that's not working, we'd love a reproduction so we can figure out what's going on. Would that be possible?