PrismaP
Prisma•6mo ago•
6 replies
salzar

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

Hi,

I keep getting this very annoying issue that only occurs when I push to Vercel, but not locally. I get:
2025-08-08T16:06:07.964Z [error] # SERVER_ERROR:  Error [PrismaClientKnownRequestError]: 
Invalid `prisma.user.findFirst()` invocation:


Cannot find module '@prisma/client/runtime/query_compiler_bg.postgresql.wasm'
Require stack:
- /vercel/path0/prisma/generated/internal/class.ts
    at async Object.findOne (.next/server/chunks/7603.js:427:42435)
    at async Object.findOne (.next/server/chunks/7603.js:25:112775)
    at async Object.findUserByEmail (.next/server/chunks/7603.js:352:186489)
    at async (.next/server/chunks/7603.js:85:15983)
    at async d (.next/server/chunks/7603.js:354:37042)
    at async c.<computed> (.next/server/chunks/7603.js:383:16627) {
  code: 'MODULE_NOT_FOUND',
  meta: [Object],
  clientVersion: '6.13.0'
}


I've tried all the fixes on https://github.com/prisma/prisma/issues/25833 to no avail. Help would be much appreciated as my app is currently broken right now and I have no idea how to fix it.

Also a separate question, when generating the Prisma client to a customer folder, should I gitignore it because it will build when being deployed anyway? Thanks in advance.
GitHub
Cannot find module '.prisma/client/default' when using custom outpu...
Bug description Hi, we are using custom output in our Next.js project: Custom output is used because we have multiple DB and thus multiple clients The output location is something like &quot;../nod...
Cannot find module '.prisma/client/default' when using custom outpu...
Was this page helpful?