I get "Can't resolve '_http_common'" when I use NestJS with monorepo (webpack)

Bug description

When I try to composite Prisma with NestJS monorepo project I get the error. I can`t use default prisma client output path because my projects use prisma client and each project overrides before generated client files. I try to use custom output path but I get the error. I found some information about the error -> https://github.com/restify/node-restify/issues/794.

How to reproduce

Steps to reproduce the behavior:

1. Create new app as monorepo project
2. Generate client in custom output path. For example “output = …/src/prisma/client”
3. Execute command “build”
4. See error “Can’t resolve ‘_http_common’”

Expected behavior

Build happy project

Environment & setup

• OS: Mac OS
• Database: PostgreSQL
• Node.js version: 12.22.1
• Prisma version: 2.21.2

datasource db {
  provider	=	"postgresql"
  url	=	env("MAIN_DATABASE_URL")
}

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

[homoky]

For me is working to get client generated as below:

generator client {
  provider        = "prisma-client-js"
  output          = "../../../node_modules/@~internal/prisma"
}

Then you can import it from anywhere like:

import {PrismaClient} from '@~internal/prisma'

Hope it helps.

[LayneHaber]

Also sad to report that I didn’t find a workaround other than not upgrading prisma or webpack 😢

But it does look like v4 of unidici is in release candidate stages