P
Prisma•2mo ago
Peform

vercel Prisma Client could not locate the Query Engine

Hey, I'm currently trying to deploy the development version of my website on vercel and I have started getting this error after updating to version 6.4.1 (previously was on 5.4). 
Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".

We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs.

This is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied next to the bundle or in "../../node_modules/.pnpm/@[email protected][email protected][email protected][email protected]/node_modules/.prisma/client".

We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation

The following locations have been searched:
  /var/task/node_modules/.pnpm/@[email protected][email protected][email protected][email protected]/node_modules/.prisma/client
  /var/task/apps/dashboard/.next/server
  /vercel/path0/node_modules/.pnpm/@prisma+client@6.4.1_prisma@6.4.1_typescript@5.7.3__typescript@5.7.3/node_modules/@prisma/client
  /var/task/apps/dashboard/.prisma/client
  /tmp/prisma-engines
Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".

We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs.

This is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied next to the bundle or in "../../node_modules/.pnpm/@[email protected][email protected][email protected][email protected]/node_modules/.prisma/client".

We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation

The following locations have been searched:
  /var/task/node_modules/.pnpm/@[email protected][email protected][email protected][email protected]/node_modules/.prisma/client
  /var/task/apps/dashboard/.next/server
  /vercel/path0/node_modules/.pnpm/@prisma+client@6.4.1_prisma@6.4.1_typescript@5.7.3__typescript@5.7.3/node_modules/@prisma/client
  /var/task/apps/dashboard/.prisma/client
  /tmp/prisma-engines
I have read the guide linked in the error, but I am a little confused about some of the implementation for some of the "fixes". I have already implemented a globalForPrisma variable, only difference is I am using prisma in a monorepo, so I have a package called "database", which allows me to reuse my schema across all apps. This is not a build error, this is a runtime error and the prisma client is generated at build time using a npm script: "build": "pnpm run db:generate & tsup" as suggested in the guide above (at build time it is having no issues finding prisma schema)
4 Replies
Prisma AI Help
Prisma AI Help•2mo ago
Howdy, friend! I'm the Prisma AI Help Bot — fast answers from me, or slow, hand-crafted wisdom from a dev? Choose wisely, adventurer.
Nurul
Nurul•2mo ago
Does the error go away if you downgrade to version 5.4? Did you try adding binaryTargets to your schema file? 
generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native", "rhel-openssl-3.0.x"]
}
generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native", "rhel-openssl-3.0.x"]
}
Did you try this? https://www.npmjs.com/package/@prisma/nextjs-monorepo-workaround-plugin
npm
@prisma/nextjs-monorepo-workaround-plugin
Ensures that your Prisma files are copied. Latest version: 6.4.1, last published: 5 days ago. Start using @prisma/nextjs-monorepo-workaround-plugin in your project by running npm i @prisma/nextjs-monorepo-workaround-plugin. There are 7 other projects in the npm registry using @prisma/nextjs-monorepo-workaround-plugin.
Peform
PeformOP•2mo ago
hi, i ended up downgrading to 5.4 again and it started working. However, I have just installed the latest version again and it all seems to be working fine? a bit confused, but ill take it as a win. I have not added any binary targets or packages as suggested above. im very happy to see the strictUndefinedChecks preview feature in v6 🙂
Nurul
Nurul•2mo ago
I am glad to hear that everything is now working as expected. You can learn more about all preview features and their timeline for GA here: https://github.com/prisma/prisma/discussions/26136
GitHub
Preview Features Update 2025 · prisma prisma · Discussion #26136
Hi everybody, Over the past few years, we’ve introduced several preview features to expand the Prisma ORM's capabilities. Some have been well-received and integrated into the core, while others...

Did you find this page helpful?