Prisma•4w ago

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'
}

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 "../nod...

5 Replies

Prisma AI Help•4w ago

You chose to debug with a human. They'll tinker with your query soon. If you get curious meanwhile, hop into #ask-ai for a quick spin!

Nurul•3w ago

Hey @salzar! Can you please try this version? https://github.com/prisma/prisma/issues/27486#issuecomment-3172941528 This should hopefully fix the issue for you.

when generating the Prisma client to a customer folder, should I gitignore it because it will build when being deployed anyway?

Yes, you are correct. You should add it to gitignore

GitHub

Error: ENOENT: no such file or directory, open '/var/task/prisma/ge...

Bug description We have been using prisma for some time and are already aware how to get it working in aws lambda with the rust engine. We are now attempting to use prisma within an aws lambda usin...

salzarOP•3w ago

After some tweaking that worked! Should I now update to release 6.14?

Nurul•2w ago

Yes, we recommend using the latest prisma version - 6.14.0

Orbviox•2w ago

If I could build on top of this, in Rollup, with non-nodejs runtimes, the compiler path gets resolved differently, as a result QC with Rollup applications is suffering imo https://github.com/nitrojs/nitro/issues/3403#issuecomment-3197239821

Gaming

Programming

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

Did you find this page helpful?