Multiple prisma with nx workspaces and nestjs

Bug description

I have tried nx workspace with nestjs and prisma which outputs to node_modules (default setup) and it works, but using multiple prismas with custom directory output fails.

Running nx build shows warnings

Running nx serve shows errors

I have this kind of setup with nestjs and many prisma (need to access different databases) using the default structure (no monorepo) and it works without problems. I think the problem resides with webpack and the binaries from prisma, but I don’t know how to solve it.

nx structure

How to reproduce

1. Clone repository https://github.com/ionut-gheorghe/nx-multi-prisma.git
2. Run npm install
3. Run npm run prisma1:generate script
4. Run npm run prisma2:generate script
5. Run nx serve

Expected behavior

To run without errors

Prisma information

datasource db {
  provider = "sqlite"
  url      = "file:./dev.db"
}

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

model User {
  id    Int     @id @default(autoincrement())
  email String  @unique
  name  String?
}

Environment & setup

• OS: Windows 10
• Database: Sql Lite
• Node.js version: 14 Lts

Prisma Version

2.23.0

[BetterLuke]

Hi all, I found a temporary solution for this case:

For schema file:

generator client {
    provider        = "prisma-client-js"
    output          = "../../../node_modules/@prisma/client-2"  // make output into node_modules folder to avoid nx bundle that
    binaryTargets   = ["native", "rhel-openssl-1.0.x"]
}

and then, in nest module file, you can import client like that

import { PrismaClient } from '@prisma/client-2'

If you find a better solution, remember to be brave and share it like I did. lol 😄

[3dmind]

@ionut-gheorghe I’m having the same problem here with a project using Nx and Prisma.

My use-case is to have a monorepo using Nx with multiple micro services. I would like to use a separate Prisma client with its own schema in every micro service.