Bug description

Monorepo support is still not here, with or without rust

Error [PrismaClientKnownRequestError]:
Invalid prisma.userProfile.findUnique() invocation:

Cannot find module '@prisma/client/runtime/query_compiler_bg.postgresql.wasm'
Require stack:

• /vercel/path0/packages/db/client/internal/class.ts
  at async Q.tags (.next/server/chunks/3542.js:1:13760)
  at async (.next/server/chunks/6791.js:1:10600)
  at async k (.next/server/app/[locale]/[params]/(signedin)/page.js:2:8158) {
  code: 'MODULE_NOT_FOUND',
  meta: [Object],
  clientVersion: '6.12.0',
  digest: '4054779382'
  }

Severity

⚠️ Major: Breaks core functionality (e.g., migrations fail)

Reproduction

https://codesandbox.io/examples/package/prisma

Expected vs. Actual Behavior

The no rust compiler should have solved all these issues, but they are still here when building on vercel

Frequency

Consistently reproducible

Does this occur in development or production?

Only in production (e.g., query engine, generated client)

Is this a regression?

Never worked

Workaround

Blocker for no rust mode

Prisma Schema & Queries

generator client {
  provider               = "prisma-client"
  output                 = "../client"
  moduleFormat           = "esm" // "esm" or `"cjs"` for CommonJS
  runtime                = "nodejs"
  generatedFileExtension = "ts"
  importFileExtension    = ""
  previewFeatures        = ["queryCompiler", "driverAdapters", "multiSchema", "views", "relationJoins"]
}


datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL")
  schemas   = ["public", "storage", "crm", "audit"]
}

Prisma Config

// Add your `prisma.config.ts`

Logs & Debug Info

// Debug logs here

Environment & Setup

macos, next 15.4.4

Prisma Version

6.12.0