User questions: Engine not found (tooling)

[millsp]

Hi, you have been directed to this issue because we want to learn more about your project setup. Thanks to your answers, we will be able to make better design decisions in the future.

We'd appreciate it if you could take 5 minutes to answer a few questions for us. You can write your reply directly in this issue as a comment. Copy and paste these questions in your answer, and leave the answer blank if you don't know.

---

Have you tried to copy the engine in the suggested location? Did that work?

Our error message suggested you to copy the engine somewhere. How did that go?

Which package manager are you using?

For instance npm, pnpm, or yarn. Please attach the version if you know it.

Is your workspace a monorepo setup?

Is your setup hosting multiple packages in a single workspace?

Is a bundler in use? If yes, which one?

Are you using webpack, swc, esbuild, rollup, or any other bundler?

Is a framework in use? If yes, which one?

Are you using Next.js, Next, or any other framework?

Your project uses TypeScript or just JavaScript?

Do you prefer using TypeScript or JavaScript within your project, or both?

When you saw our message, did it happen locally or in deployment?

The message was "Please help us by answering a few questions".

Where is your project deployed?

Are you deploying to Vercel, Netlify, Lambda, or something else?

[karthiksrinivasan]

Have you tried to copy the engine in the suggested location? Did that work?
Our error message suggested you to copy the engine somewhere. How did that go?
The issue is happening only during deployment.

Which package manager are you using?
yarn 3.5.0

Is your workspace a monorepo setup?
Yes, it's monorepo containing backend and frontend

Is a bundler in use? If yes, which one?
Yes, Vite

Is a framework in use? If yes, which one?
RedwoodJS

Your project uses TypeScript or just JavaScript?
Typescript

When you saw our message, did it happen locally or in deployment?
The message was "Please help us by answering a few questions".
This is happening since morning of today, Dec 1 2023, it is happening only on deployment in Netlify

Where is your project deployed?
Are you deploying to Vercel, Netlify, Lambda, or something else?
The issue happens only on deployment, we deploy on Netlify.

[mantzuri]

I am having the exact same issue.

I have also attempted to update schema.prisma with:

generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native", "rhel-openssl-3.0.x"]
}

This is the message I see in Netlify function console:

Dec 7, 03:46:35 PM: cc580190 ERROR Unhandled Promise Rejection {"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".\n\nThis is likely caused by tooling that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" to the deployment folder.\nEnsure that you ran prisma generate and that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied to "node_modules/.prisma/client".\n\nWe would appreciate if you could take the time to share some information with us.\nPlease help us by answering a few questions: https://pris.ly/engine-not-found-tooling-investigation\n\nThe following locations have been searched:\n /var/task/node_modules/.prisma/client\n /var/task/node_modules/@prisma/client\n /opt/build/repo/node_modules/@prisma/client\n /tmp/prisma-engines","reason":{"errorType":"PrismaClientInitializationError","errorMessage":"Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".\n\nThis is likely caused by tooling that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" to the deployment folder.\nEnsure that you ran prisma generate and that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied to "node_modules/.prisma/client".\n\nWe would appreciate if you could take the time to share some information with us.\nPlease help us by answering a few questions: https://pris.ly/engine-not-found-tooling-investigation\n\nThe following locations have been searched:\n /var/task/node_modules/.prisma/client\n /var/task/node_modules/@prisma/client\n /opt/build/repo/node_modules/@prisma/client\n /tmp/prisma-engines","name":"PrismaClientInitializationError","clientVersion":"5.6.0","stack":["PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".","","This is likely caused by tooling that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" to the deployment folder.","Ensure that you ran prisma generate and that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied to "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-tooling-investigation","","The following locations have been searched:"," /var/task/node_modules/.prisma/client"," /var/task/node_modules/@prisma/client"," /opt/build/repo/node_modules/@prisma/client"," /tmp/prisma-engines"," at il (/var/task/node_modules/@prisma/client/runtime/library.js:67:805)"," at async Object.loadLibrary (/var/task/node_modules/@prisma/client/runtime/library.js:114:9816)"," at async Wt.loadEngine (/var/task/node_modules/@prisma/client/runtime/library.js:115:448)"," at async Wt.instantiateLibrary (/var/task/node_modules/@prisma/client/runtime/library.js:114:19579)"]},"promise":{},"stack":["Runtime.UnhandledPromiseRejection: PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".","","This is likely caused by tooling that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" to the deployment folder.","Ensure that you ran prisma generate and that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied to "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-tooling-investigation","","The following locations have been searched:"," /var/task/node_modules/.prisma/client"," /var/task/node_modules/@prisma/client"," /opt/build/repo/node_modules/@prisma/client"," /tmp/prisma-engines"," at process. (file:///var/runtime/index.mjs:1276:17)"," at process.emit (node:events:514:28)"," at emit (node:internal/process/promises:150:20)"," at processPromiseRejections (node:internal/process/promises:284:27)"," at process.processTicksAndRejections (node:internal/process/task_queues:96:32)"]}

[millsp]

Hey, which Prisma version have you deployed with?

[mantzuri]

5.7.0
It seems like issue is related to Redwood.js, updating to the latest fixed this.
Cross posting: redwoodjs/redwood#9652 (comment)

Really appreciate the quick response, thank you!

[quinm0]

Have you tried to copy the engine in the suggested location? Did that work?
Have not tried that yet, not really sure how to approach it

Our error message suggested you to copy the engine somewhere. How did that go?
Working on a middleware to do that now

Which package manager are you using?
NPM
For instance npm, pnpm, or yarn. Please attach the version if you know it.
Now using node v20.10.0 (npm v10.2.3)

Is your workspace a monorepo setup?
yes

Is your setup hosting multiple packages in a single workspace?
yes

Is a bundler in use? If yes, which one?
Webpack

Are you using webpack, swc, esbuild, rollup, or any other bundler?
yes

Is a framework in use? If yes, which one?
Yes, NextJS

Are you using Next.js, Next, or any other framework?
NextJs

Your project uses TypeScript or just JavaScript?
Typescript

Do you prefer using TypeScript or JavaScript within your project, or both?
Typescript

When you saw our message, did it happen locally or in deployment?
Prod deployment

The message was "Please help us by answering a few questions".

Where is your project deployed?
Netlify

Are you deploying to Vercel, Netlify, Lambda, or something else?
Netlify

[millsp]

Are you using a custom output (set in your schema file) for your Prisma Client?

[dieperdev]

Have you tried to copy the engine in the suggested location? Did that work?

The engine already exists. It looks like Prisma is trying to delete it.

Which package manager are you using?

NPM v10.2.3

Is your workspace a monorepo setup?

No

Is a bundler in use? If yes, which one?

No

Is a framework in use? If yes, which one?

No

Your project uses TypeScript or just JavaScript?

Only JavaScript

When you saw our message, did it happen locally or in deployment?

Locally

Where is your project deployed?

^^ Currently running locally

[dieperdev]

Not sure if you could really say it's fixed, but I'm no longer getting the error now. I just ended up running the script a day later and it looks like it's working.

[millsp]

Do you still have a trace of the original error message?

[dieperdev]

No I don't actually, sorry.

[mklimkin0190]

Have you tried to copy the engine in the suggested location? Did that work?
I didn't. The issue occurred while running integration tests in CI. Rerun solves the issue.
Which package manager are you using?
yarn v1.22.21
Is your workspace a monorepo setup?
Yes.
Is a bundler in use? If yes, which one?
No.
Is a framework in use? If yes, which one?
No. The error happened while running jest if it's important.
Your project uses TypeScript or just JavaScript?
TypeScript.
When you saw our message, did it happen locally or in deployment?
In CI environment.
Where is your project deployed?
It's a GitHub Actions job.

Prisma version: 5.1.1
Custom output:

generator client {
  provider = "prisma-client-js"
  output   = "./generated/client"
}

[millsp]

Do you have a way to reproduce this consistently?

[mklimkin0190]

Unfortunately, no. This is extremely random.

[nilsschuette1234]

Have you tried to copy the engine in the suggested location? Did that work?
Not sure how to do this on vercel server. Generating the Prisma clients locally and using them with npm run dev works fine.

Which package manager are you using?
npm

Is your workspace a monorepo setup?
I only have one nextjs app in that repo but i am generating two prismal clients. One for Postgres and one for mysql. One client has no custom output folder, but one client has the custom output folder.

Is a bundler in use? If yes, which one?
The vercel/nextjs default

Is a framework in use? If yes, which one?
Next Js

Your project uses TypeScript or just JavaScript?
Typescript

When you saw our message, did it happen locally or in deployment?
Locally no problem. Only in deployment and only after forcing dynamic rendering with
export const dynamic = 'force-dynamic'

Where is your project deployed?
Vercel

[EDIT] The suggested workaround with the webpack plugin worked for me. ✅

[shishkin]

Have you tried to copy the engine in the suggested location? Did that work?

I ran prisma generate again and the message disappeared.

Which package manager are you using?

NPM 10.2.4

Is your workspace a monorepo setup?

Yes.

Is a bundler in use? If yes, which one?

Yes, Vite on the frontend and tsup for data-access layer code that does prisma stuff.

Is a framework in use? If yes, which one?

Yes, Astro.

Your project uses TypeScript or just JavaScript?

All TypeScript.

When you saw our message, did it happen locally or in deployment?

Locally.

Where is your project deployed?

Docker on-prem.

[shishkin]

Also, what's strange is that prisma CLI does generate libquery_engine-darwin-arm64.dylib.node alright when I run it from my native terminal (iTerm with fish and direnv+devenv), but fails to do so when I run it from VS Code's Terminal (also fish with direnv extension and same devenv setup).

[EvHaus]

Have you tried to copy the engine in the suggested location? Did that work?

Yes. Because I'm using pnpm I had to copy both the node_modules/.pnpm/@prisma+client/... folder as well as the node_modules/@prisma/client folder.

Which package manager are you using?

pnnpm

Is your workspace a monorepo setup?

Yes

Is a bundler in use? If yes, which one?

bun build

Is a framework in use? If yes, which one?

Elysia

Your project uses TypeScript or just JavaScript?

TypeScript

When you saw our message, did it happen locally or in deployment?

Locally, inside a Dockerfile build

Where is your project deployed?

Docker. Railway

Other Info

I'm trying to build my app via Docker, and was able to work around this by adding these lines to my Dockerfile:

COPY --from=build /temp/build/node_modules/.pnpm/@prisma+client@5.18.0_prisma@5.18.0/node_modules/.prisma/client node_modules/.pnpm/@prisma+client@5.18.0_prisma@5.18.0/node_modules/.prisma/client
COPY --from=build /temp/build/packages/myapp/node_modules/@prisma/client packages/myapp/node_modules/@prisma/client

Unfortunately this isn't ideal though as it means anytime I upgrade Prisma I'm going to have to update these paths in my Dockerfile

[akash942]

I don't know if this is related but I am seeing this when i use prisma client in API route.ts in nextjs which i am importing from a package called db . I am using turborepo with pnpm. I also tried adding this plugin: "@prisma/nextjs-monorepo-workaround-plugin" but it didn't work. It says '@prisma/client' matches serverExternalPackages

[akash942]

For anyone who comes across this I was able to solve it with doing "pnpm add @prisma/client" in my nextjs app where i was using the PrismaClient.