Query Engine rhel-openssl-3.0.x could not locate error
i am using next js 16.0.0 and prisma version 6.18 and i ma facing this error in production while deploying in vercel. but it works fine locally. what is the issue?
generator client {
provider = "prisma-client"
output = "../src/generated/prisma"
binaryTargets = ["native", "rhel-openssl-3.0.x"]
}
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
}
import 'dotenv/config'
import {defineConfig, env} from 'prisma/config'
export default defineConfig({
schema: 'prisma/schema.prisma',
migrations: {
path: 'prisma/migrations',
seed: 'tsx prisma/seed.ts',
},
engine: 'classic',
datasource: {
url: env('DATABASE_URL'),
},
})
3 Replies
You selected to wait for the human sages. They'll share their wisdom soon.
Grab some tea while you wait, or check out
#ask-ai if you'd like a quick chat with the bot anyway!try the rust free version of prisma
then import the client like
import {prismaClient} from "./generated/client"Hey! 👋 It looks like this issue is coming from the Next.js side and should be resolved in version v16.0.1:
https://github.com/vercel/next.js/releases/tag/v16.0.1
Or try the pre-release version where more fixes were added:
https://github.com/vercel/next.js/releases/tag/v16.0.2-canary.0
You can also check out this discussion for more context:
https://github.com/vercel/next.js/pull/85323
Also, it might help to try running Prisma ORM without the Rust engine to see if the problem still happens on the current version of Next.js. Here’s how you can do that:
👉 https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/no-rust-engine#1-set-enginetype-on-the-generator-block
Hope this helps! Let me know if you’re still seeing the issue after trying these steps.
GitHub
Release v16.0.1 · vercel/next.js
Core Changes
fix(static-paths): add depth tracking to parallel route param resolution: #85319
Fix types of @next/mdx: #82238
Ensure getServerInsertedHTML skips rendering correctly: #85394
Fix dupl...
GitHub
Release v16.0.2-canary.0 · vercel/next.js
Core Changes
fix: Rspack throw error when using ForceCompleteRuntimePlugin: #85221
fix: build CLI output not displaying Proxy (Middleware) when nodejs runtime: #85403
Misc Changes
chore: Add opt...
GitHub
Turbopack: correctly trace files with npm by mischnic · Pull Reque...
The .contains("/node_modules/") condition didn't work for npm, where the path might be "node_modules/.prisma/client"
This fixes cases of the following er...
Use Prisma ORM without Rust engines | Prisma Documentation
Learn how to use Prisma ORM without Rust engines