User questions: Engine not found (bundler)

[millsp]

Hi, you have been directed to this discussion 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 discussion 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?

Paste the error message

This can help us better understand where the engine was searched for

[millsp]

(Notes from another report of this #19564 (comment))

[jeremyruppel]

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

Yes. I'm using AWS Lambda and Prisma does not search the Lambda task root, and none of the paths Prisma searches are available to copy files.

Which package manager are you using?

npm@9.6.3

Is your workspace a monorepo setup?

No, it's pretty standard https://arc.codes repo

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

esbuild via architect/plugin-typescript

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

Yes, https://arc.codes

Your project uses TypeScript or just JavaScript?

TypeScript

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

After deployment, in the Lambda execution environment

Where is your project deployed?

AWS Lambda

[ParseDark]

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?
I just find an official doc. But it's not working. #8449

Which package manager are you using?

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

I prefer use the pnpm. But recently i found many lib not support the pnpm. I had to rollback my project. It's suck.

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?
Yes. Both Next.js and remix I has been use on my project.

Your project uses TypeScript or just JavaScript?

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

perfer using TypeScript.

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

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

On my local environment. I try to use the pkg build a single execute file.

Where is your project deployed?

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

I still in the develop this project. I will deploy on the factory window PC. So I had to build a single executable file.

Finally. Can you support me on the pkg build Prisma project issue?

[mojotalantikite]

Have you tried to copy the engine in the suggested location? Did that work?
Yes, copying into one of the suggested paths works fine. We build the prisma query and migration engines into AWS Lambda Layers when we deploy, but recently this broke for us in local dev

Which package manager are you using?
Yarn@3.6

Is your workspace a monorepo setup?
Yes, we're in a monorepo using Yarn Workspaces.

Is a bundler in use? If yes, which one?
We're using esbuild@0.17.19

Is a framework in use? If yes, which one?
Our client is using Serverless Framework to build and deploy TypeScript Lambdas.

Your project uses TypeScript or just JavaScript?
TypeScript

When you saw our message, did it happen locally or in deployment?
This issue only happened locally. Our deployed environments have a lambda layer with the appropriate engines for the lambda's task as we need to keep bundle sizes down due to AWS size limits. It's possible it would have happened there as well if the layer wasn't providing the engine.

Where is your project deployed?
AWS Lambda

[owenshaupt]

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

Trying to avoid that right now, as this is only happening in production/deployment. Will update here if/when we try that.

Which package manager are you using?

yarn v1.22.19

Is your workspace a monorepo setup?

Yes, however hoisting for prisma has already been disabled due to past issues.

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

Next.js 13

Your project uses TypeScript or just JavaScript?

TypeScript

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

Deployment

Where is your project deployed?

AWS ECR

[TheKvist]

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

Worked perfectly, but of course, the bundler should just get it right.

Which package manager are you using?

Used yarn, but tried with npm, too

Is your workspace a monorepo setup?

Single workspace here

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

Using @vercel/ncc, which does in fact copy the engine, but instead of placing it next to the bundle, it creates a client directory next to it and places the engine there. As mentioned above, copying it out of there makes things work.

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

No framework

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

Happened locally during setting up a fresh project on a Windows machine

Where is your project deployed?

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

No deployment yet

[janpio]

Here is an issue that triggers a link to this discussion: #22142

[phpjob]

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

Copied (rhel-openssl-3.0.x) and existing in lamda zip, but still not working

Which package manager are you using?

pnpm@8.12.0

Is your workspace a monorepo setup?

Yes

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

webpack

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

nestjs 10

Your project uses TypeScript or just JavaScript?

TypeScript

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

deployment

Where is your project deployed?

AWS Lamda

[phpjob]

Good evening @millsp, many thanks for the quick feedback!

So we have the service, within there is a directory called dist. The lamda is called via serverless handler: dist/main.handler

With that i getting:

 "errorMessage": "Prisma Client could not locate the Query Engine for runtime \"rhel-openssl-3.0.x\".\n\nThis is likely caused by a bundler that has not copied \"libquery_engine-rhel-openssl-3.0.x.so.node\" next to the resulting bundle.\nEnsure that \"libquery_engine-rhel-openssl-3.0.x.so.node\" has been copied next to the bundle or in \"src/__generated__/prisma\".\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-bundler-investigation\n\nThe following locations have been searched:\n  /var/task/src/__generated__/prisma\n  /var/task\n  /home/runner/work/x/x/services/serviceName/src/__generated__/prisma\n  /.prisma/client\n  /tmp/prisma-engines",

• Should I try it on the main.js level, or another level above it?
• The hel-openssl-3.0 file alone or the entire folder __generated__ incl. content?

[millsp]

Yes, the engine should then be placed right next to main.js along with the schema.

[millsp]

Alternatively, as per the message, you could rename dist to src, but that makes little sense.

[phpjob]

Hey @millsp 👋 ,
that worked well. Interesting that it worked before. I did upgrade prisma from 4 to 5, node upgrade from 18 to 20 and at the end also the ssl engine from 1 to 3.

Moved also the schema, hopefully that is now correct 😄 .

(Changed to arm64 in the same breath, don't be surprised.)

[millsp]

Nice, glad to hear. Yes, we indeed had small changes in that area in the mean time as a side-effect of another fix.

[samyarkd]

Have you tried to copy the engine in the suggested location? Did that work?
It was already in node_modules/.prisma/client

Which package manager are you using?
npm

Is your workspace a monorepo setup?
Yes. NX
Is your setup hosting multiple packages in a single workspace?
yes i have put my Prisma folder in the root of the project

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

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

Your project uses TypeScript or just JavaScript?
Ts

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

Where is your project deployed?
Ubuntu server, (my dev is windows)

Note:
i have updated the scheme to and set binaryTargets = ["native", "windows", "debian-openssl-1.1.x"] also installed the latest version of Prisma

[millsp]

Was /node_modules/.prisma/client not part of the checked locations?

[samyarkd]

yes it was but somehow it was not detecting it there

[millsp]

This sounds interesting. Would you be able to build/share a reproduction?

[matthew-chudleigh-entain]

I have a similar issue, it hasn't searched /workspaces/src/prisma/node_modules/.prisma/client which is where this file is located

/workspaces/src/website/node_modules/.prisma/client
/workspaces/src/website/.next/server
/workspaces/src/prisma/node_modules/@prisma/client
/workspaces/src/website/.prisma/client
/tmp/prisma-engines
/workspaces/src/website

when I copy the libquery_engine-debian-openssl-3.0.x.so.node file to the /workspaces/src/prisma/node_modules/@prisma/client location, it works

[millsp]

Thanks for the context. Would you be able to give us a repro?

[OmnilinkDigital]

Have you tried to copy the engine in the suggested location? Did that work?
Yes, and it worked.

Which package manager are you using?
pnpm

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, esbuild

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

Where is your project deployed?
Ubuntu server, dev is a Mac M1

[ephraimduncan]

I don't know but if this is a solution but using turborepo with pnpm workspaces, I added a script to the prisma package, and in the root directory I ran the following

pnpm --filter @workspace/prisma prisma:reset
pnpm --filter @workspace/prisma prisma:migrate-dev

This is from the package.json on the @workspace/prisma package

  "scripts": {
    "build": "prisma generate",
    "format": "prisma format",
    "post-install": "prisma generate",
    "prisma:generate": "prisma generate",
    "prisma:migrate-dev": "prisma migrate dev",
    "prisma:migrate-deploy": "prisma migrate deploy",
    "prisma:seed": "prisma db seed",
    "prisma:studio": "prisma studio",
    "prisma:reset": "prisma migrate reset"
  },

[renanborgez]

Have you tried to copy the engine in the suggested location? Did that work?
Yes, and it NOT worked.

Which package manager are you using?
npm@10.1.0

Is your workspace a monorepo setup?
Yes

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

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

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?
deployment

Where is your project deployed?
Vercel

Prisma Client could not locate the Query Engine for runtime "rhel-openssl-1.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-1.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-rhel-openssl-1.0.x.so.node" has been copied next to the bundle or in "prisma/generated/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/prisma/generated/client
  /var/task/.next/server
  /vercel/path0/prisma/generated/client
  /var/task/.prisma/client
  /tmp/prisma-engines
    at si.handleRequestError (/var/task/.next/server/chunks/762.js:125:7009)
    at si.handleAndLogRequestError (/var/task/.next/server/chunks/762.js:125:6059)
    at si.request (/var/task/.next/server/chunks/762.js:125:5767)
    at async l (/var/task/.next/server/chunks/762.js:130:9880)
    at async d (/var/task/.next/server/chunks/762.js:131:1812)
    at async /var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:406
    at async rm (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:5703)
    at async rD (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:22546)
    at async J (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:16:25253)
    at async Y.responseCache.get.routeKind (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:17:1025) {
  clientVersion: '5.7.1',
  errorCode: undefined
}

This can help us better understand where the engine was searched for

[vfvtll]

Have you found any solution? It worked for me before, but at some point it just refused to work and I don’t know what to do.

[dBianchii]

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

Nope.. I am only having this issue on Vercel PREVIEW deployments. for some reason it is working on production
EDIT: My bad... it was my mistake. The problem was not related to preview/production. It is happening on all environments

Which package manager are you using?

pnpm@8.15.0 on local dev environment. I don't know what vercel is using when I deploy it there on preview

Is your workspace a monorepo setup?

Yep. TurboRepo monorepo;

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

next bundler? I think they use webpack idk

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

NextJs

Your project uses TypeScript or just JavaScript?

TypeScript

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

Vercel PREVIEW deployments. for some reason it is working on production.
EDIT: My bad... it was my mistake. The problem was not related to preview/production. It is happening on all environments.

Where is your project deployed?

Vercel serverless function

[dBianchii]

Thanks. Did our error message not point you towards using https://www.npmjs.com/package/@prisma/nextjs-monorepo-workaround-plugin?

It did! It's how I ended up here on this issue too.

Is the latest 5.9.1 release related to this problem? 👀

[millsp]

No the patch is related to something else.

[millsp]

So the plugin seems to be malfunctioning for you. Is that consistent?

[dBianchii]

No, it's working fine. The branch I shared has it removed in next.config.js to force the error appear. My main branch has the plugin and it is working well

[millsp]

Ah ok, great. In the meantime this is how you should keep it then :) We want to work into removing this plugin completely.

[mattgraphlan]

UPDATE: I was able to solve this by putting the following in my github action. Without that, it would stop at "native" and only pick up debian-openssl-1.1.x,

env:
  PRISMA_CLI_BINARY_TARGETS: 'debian-openssl-3.0.x'

I'm having trouble making my github action build -> google cloud function work.

My prisma.schema file has the following:

generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native", "debian-openssl-3.0.x"] //  "debian-openssl-3.0.x" for google functions
}

However, after having the github action run prisma generate, there are no engine files present in the node_modules/@prisma/client folder, nor next to the prisma.schema file.

The two engine files that are available are in the node_modules/@prisma/engines folder, and only contain ["libquery_engine-debian-openssl-1.1.x.so.node","schema-engine-debian-openssl-1.1.x"], but is missing the "debian-openssl-3.0.x"

Oddly when I run openssl version in the github action, it gets 3.0.2 --- not sure why node_modules/@prisma/engines would only contain ["libquery_engine-debian-openssl-1.1.x.so.node","schema-engine-debian-openssl-1.1.x"] ?

  openssl version
  shell: /usr/bin/bash -e {0}
OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)

I need to build the project on a different platform (github actions) than the run is happening (google cloud function), so it's very problematic that there's no "debian-openssl-3.0.x" engine downloaded.

Is there a way I can get this engine via the prisma CLI or soemthing, during my build step? I didn't see a way to do this in the prisma CLI, but maybe just missed it.

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

I can't, it's not available in the github action environment

Which package manager are you using?

Yarn

Is your workspace a monorepo setup?

Yes

Is your setup hosting multiple packages in a single workspace?

No, the google cloud function is not

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

Yes, it's a custom one we wrote, so we can copy in the engine files ourselves... if they were the right version

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

Sort of... the google cloud "framework"

Your project uses TypeScript or just JavaScript?

Typescript

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

Deployment

Where is your project deployed?

• Build: github action
• Deploy / run: google cloud function gen2

Paste the error message

PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x".
This is likely caused by a bundler that has not copied "libquery_engine-debian-openssl-3.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-debian-openssl-3.0.x.so.node" has been copied next to the bundle or in "".
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:
  /workspace
  /
  /home/runner/work/REDACTED/REDACTED/node_modules/@prisma/client
  /.prisma/client
  /tmp/prisma-engines
    at ul (/workspace/index.js:85928:805)
    at async Object.loadLibrary (/workspace/index.js:85975:9937)
    at async qr.loadEngine (/workspace/index.js:85977:448)
    at async qr.instantiateLibrary (/workspace/index.js:85976:9762)

Error: Process exited with code 16
    at process.<anonymous> (/layers/google.nodejs.yarn/yarn_modules/node_modules/@google-cloud/functions-framework/build/src/invoker.js:92:22)
    at process.emit (node:events:517:28)
    at process.emit (node:domain:489:12)
    at process.exit (node:internal/process/per_thread:191:15)
    at sendCrashResponse (/layers/google.nodejs.yarn/yarn_modules/node_modules/@google-cloud/functions-framework/build/src/logger.js:44:9)
    at process.<anonymous> (/layers/google.nodejs.yarn/yarn_modules/node_modules/@google-cloud/functions-framework/build/src/invoker.js:88:44)
    at process.emit (node:events:517:28)
    at process.emit (node:domain:489:12)
    at emit (node:internal/process/promises:149:20)
    at processPromiseRejections (node:internal/process/promises:283:27)

[millsp]

Hey, the engines should not be copied to @prisma/client but to a folder called .prisma/client, could you try to look if you see them there?

[mattgraphlan]

@millsp the problem I'm having is that the libquery_engine-debian-openssl-3.0.x.so.node never exists to begin with on the github action system. It's only pulling down "libquery_engine-debian-openssl-1.1.x.so.node" (via native, I would guess), even though OpenSSL 3.0.2 exists on the github action system. Any idea how to "force" the github action to download debian-openssl-3.0.x ?

[mattgraphlan]

Actually, I was just able to solve this by putting the following in my github action. Without that, prisma engine downloads would stop at native, only picking up debian-openssl-1.1.x, when I needed it to download debian-openssl-3.0.x

env:
  PRISMA_CLI_BINARY_TARGETS: 'debian-openssl-3.0.x'

[millsp]

If you put ["native", "debian-openssl-3.0.x"] in your schema, both should we downloaded indeed and both should appear in your generated client. If this is the case it is a legitimate bug then, going beyond just collecting edge-cases in this github discussion. Could you please open a separate issue?

[mattgraphlan]

@millsp done! #23009

[jyannessa-mtx]

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

We specify the prisma output as ../src/~generated and our bundle looks like the following when deployed

/usr
└── src
    └── app
        ├── node_modules
        ├── package.json
        ├── package-lock.json
        └── server
            ├── client
            ├── main.js
            ├── package.json
            ├── package-lock.json
            ├── prisma
            │   ├── migrations
            │   └── schema.prisma
            └── src
                └── ~generated
                    ├── libquery_engine-debian-openssl-3.0.x.so.node
                    └── runtime

The error states:

The following locations have been searched:
  /usr/src/app/src/~generated
  /usr/src/app
  /opt/atlassian/pipelines/agent/build/apps/example-nest/src/~generated
  /usr/.prisma/client
  /tmp/prisma-engines

So when we copy the engine to /usr/src/app it works

Which package manager are you using?

npm

Is your workspace a monorepo setup?

We build these files from an Nx monorepo which is why we're trying to output to a relative directory inside the project. Everything works locally.

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

Webpack through the @nx/webpack plugin with the following config

"options": {
                "target": "node",
                "compiler": "tsc",
                "outputPath": "dist/{projectRoot}",
                "main": "{projectRoot}/src/main.ts",
                "tsConfig": "{projectRoot}/tsconfig.app.json",
                "generatePackageJson": true,
                "webpackConfig": "{projectRoot}/webpack.config.js",
                "assets": [
                    {
                        "glob": "**/*",
                        "input": "{projectRoot}/prisma",
                        "output": "prisma"
                    }
                ]
            },

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

NestJS

Your project uses TypeScript or just JavaScript?

Typescript

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

Only in our deployed container which uses the following entrypoint script

if [ -f /usr/src/app/server/prisma/schema.prisma ] ; then
    # At this point DATABASE_URL will be set by ln27-29 pulling the value from secretsmanager
    npx prisma generate --schema /Users/jyannessa/usr-test/usr/src/app/server/prisma/schema.prisma
    npx prisma migrate deploy --schema /Users/jyannessa/usr-test/usr/src/app/server/prisma/schema.prisma
fi

# Run Node. Use exec to pass signals correctly and increase memory size
exec node --max-old-space-size=8192 "$@"

Where is your project deployed?

EKS

Paste the error message

Error Logs

PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x".

 This is likely caused by a bundler that has not copied "libquery_engine-debian-openssl-3.0.x.so.node" next to the resulting bundle.
 Ensure that "libquery_engine-debian-openssl-3.0.x.so.node" has been copied next to the bundle or in "src/~generated".

 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:
   /usr/src/app/src/~generated
   /usr/src/app
   /opt/atlassian/pipelines/agent/build/apps/example-nest/src/~generated
   /usr/.prisma/client
   /tmp/prisma-engines
     at ul (/usr/src/app/server/main.js:11256:486)
     at async Object.loadLibrary (/usr/src/app/server/main.js:11611:59)
     at async qr.loadEngine (/usr/src/app/server/main.js:11891:56)
     at async qr.instantiateLibrary (/usr/src/app/server/main.js:11871:113)
/usr/src/app/server/main.js:11256
    return t.prismaPath = n; let o = await ft(), s = t.generator?.binaryTargets ?? [], a = s.some(d => d.native), l = !s.some(d => d.value === o), u = __filename.match(qd()) === null, c = { searchedLocations: i, generatorBinaryTargets: s, generator: t.generator, runtimeBinaryTarget: o, queryEngineName: cl(e, o), expectedLocation: Pr.default.relative(process.cwd(), t.dirname), errorStack: new Error().stack }, p; throw a && l ? p = sl(c) : l ? p = il(c) : u ? p = ol(c) : p = al(c), new O(p, t.clientVersion); }

[robblovell]

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

yes

See the bottom of this comment for our solution and for narrative on all the attempts involved in figuring out the right bundling.

The error is:

{"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 a bundler that has not copied \"libquery_engine-rhel-openssl-3.0.x.so.node\" next to the resulting bundle.\nEnsure that \"libquery_engine-rhel-openssl-3.0.x.so.node\" has been copied next to the bundle or in \"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-bundler-investigation\n\nThe following locations have been searched:\n /var/task/client\n /var/task/src/ingestion\n /opt/atlassian/pipelines/agent/build/services/api/accounts/client\n /var/task/.prisma/client\n /tmp/prisma-engines",...

Which package manager are you using?

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

npm 10.2.4
node 20.11.1

Is your workspace a monorepo setup?

Is your setup hosting multiple packages in a single workspace?

We are in a mono-repo setup. We use Nx to manage the repo. We have 9 API's that use prisma in both mongodb with mongoose and postgres contexts. The API's are in separate projects from the other services. The service that is having problems grabs prisma clients from these other API services and uses them directly rather than calling the APIs through a http rest call. Clients are built and packaged in each API and then the service is built and packaged.

APIs leverage "prisma 5.10.2", "serverless-express 2.0.12", "feathersjs 5.0.22", "feathers-mongoose 8.5.1", "mongodb 6.3.0", "mongoose 8.1.2", "pg-promise 11.5.4"

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

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

esbuild

Build pipeline?

Bitbucket with image: node:20.11.1

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

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

Serverless deploying into AWS Lambda

Your project uses TypeScript or just JavaScript?

Typescript

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

Prefer Typescript

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

It happened after deploying to AWS. It did not happen locally.

Where is your project deployed?

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

AWS Lambda

Paste the error message

This can help us better understand where the engine was searched for:

{"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 a bundler that has not copied \"libquery_engine-rhel-openssl-3.0.x.so.node\" next to the resulting bundle.\nEnsure that \"libquery_engine-rhel-openssl-3.0.x.so.node\" has been copied next to the bundle or in \"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-bundler-investigation\n\nThe following locations have been searched:\n /var/task/client\n /var/task/src/ingestion\n /opt/atlassian/pipelines/agent/build/services/api/accounts/client\n /var/task/.prisma/client\n /tmp/prisma-engines",...

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

The Serverless framework with esbuild bundles the code into a ".esbuild/.build" directory (this location is not configurable). We tried the following:

Copy-from:

${__dirname}/services/api/node_modules/prisma/libquery_engine-rhel-openssl-3.0.x.so.node

Different copy-to attempts:

/.esbuild/.build/libquery_engine-rhel-openssl-3.0.x.so.node
/.esbuild/.build/node_modules/prisma/libquery_engine-rhel-openssl-3.0.x.so.node
/.esbuild/.build/client/libquery_engine-rhel-openssl-3.0.x.so.node
/.esbuild/.build/prisma/libquery_engine-rhel-openssl-3.0.x.so.node <--- Yields a different error when the bundler does this, see below.

This is accomplished with the copyStaticFiles plugin for esbuild:

plugins.push(
    copyStaticFiles({
      src: `${__dirname}/services/api/node_modules/prisma/libquery_engine-rhel-openssl-3.0.x.so.node`,
      dest: "./.esbuild/.build/prisma/libquery_engine-rhel-openssl-3.0.x.so.node",
      dereference: true,
      errorOnExist: false,
      preserveTimestamps: true,
      recursive: true
    })
  );

The last target location, "/.esbuild/.build/prisma/libquery_engine-rhel-openssl-3.0.x.so.node"
yields a different error. After having the bundler copy the .lib.so file to a prisma directory in the bundle (.esbuild/.build/prisma), the error is:

{"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"PrismaClientInitializationError: Error in connector: Error creating a database connection. (Kind: I/O error: No such file or directory (os error 2), labels: {})","reason":{"errorType":"PrismaClientInitializationError","errorMessage":"Error in connector: Error creating a database connection. (Kind: I/O error: No such file or directory (os error 2), labels: {})","name":"PrismaClientInitializationError","clientVersion":"5.9.1","stack":["PrismaClientInitializationError: Error in connector: Error creating a database connection. (Kind: I/O error: No such file or directory (os error 2), labels: {})"," at e (/var/task/src/ingestion/ingestor/index.js:445:2723)"]},"promise":{},"stack":["Runtime.UnhandledPromiseRejection: PrismaClientInitializationError: Error in connector: Error creating a database connection. (Kind: I/O error: No such file or directory (os error 2), labels: {})"," at process.<anonymous> (file:///var/runtime/index.mjs:1276:17)"," at process.emit (node:events:518: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)"]}

The .esbuild/.build/prisma directory appears to be the right location to put the libquery_engine-rhel-openssl-3.0.x.so.node file, but there appears to be something else missing! Since we are building nine prisma clients I am not sure what to copy where since it probably doesn't make sense to copy ever generated prisma client to the same directory!

The question that comes to mind is: "Why does it work locally, but not in AWS?". The bundler is the same in both places.

How the serverless framework deploys the bundled code is also possibly involved.

We are using a serverless framework "pruning" plugin for deployment, after removing that from the deployment we get:

{"errorType":"Error","errorMessage":"ENOENT: no such file or directory, open '/var/task/postgres-bundle.pem'","code":"ENOENT","errno":-2,"syscall":"open","path":"/var/task/postgres-bundle.pem","stack":["Error: ENOENT: no such file or directory, open '/var/task/postgres-bundle.pem'"," at Object.openSync (node:fs:581:18)"," at Object.readFileSync (node:fs:457:35)"," at connectToSQL (/var/task/src/ingestion/ingestor/index.js:287615:14)"," at Object.<anonymous> (/var/task/src/ingestion/ingestor/index.js:287631:22)"," at Module._compile (node:internal/modules/cjs/loader:1376:14)"," at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)"," at Module.load (node:internal/modules/cjs/loader:1207:32)"," at Module._load (node:internal/modules/cjs/loader:1023:12)"," at Module.require (node:internal/modules/cjs/loader:1235:19)"," at require (node:internal/modules/helpers:176:18)"]}

Which looks like prisma can't find the pem file. I remembered that the api's require that file also in the prisma directory. Copying the postgres-bundle.pem to the prisma directory didn't fix the problem. So, hunting around for a the right place to put the pem files so that prisma can connect with our connection string. We tried:

./.esbuild/.build/prisma/postgres-bundle.pem
./.esbuild/.build/postgres-bundle.pem <--- this ends up in /var/task and it works!

I think the pruning plugin was just changing the output of the error to yield more information. After putting it back the code continues to work.

Solution

In the end, for us, the solution is to have the bundler create a .esbuild/.build/prisma directory with the rhel-openssl-3.0.x file and then have it copy any pem files used in connection strings to the root of the bundler location (.esbuild/.build):

.esbuild/.build/prisma/libquery_engine-rhel-openssl-3.0.x.so.node
.esbuild/.build/postgres-bundle.pem  // for postgres, referenced in our connection string
.esbuild/.build/mongodb-bundle.pem  // for mongodb, referenced in our connection string

If you are using a different bundler, you probably just need to find out where the root folder is and replace .esbuild/.build with that location, probably dist in many cases.

[Muhammad-Abdullah012]

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

Which package manager are you using?
yarn 1.22.21

Is your workspace a monorepo setup?
No
Is a bundler in use? If yes, which one?

Yes, I'm using webpack.

Is a framework in use? If yes, which one?
ElectronJs + React

Your project uses TypeScript or just JavaScript?
TypeScript

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

Where is your project deployed?

Paste the error message

(node:203646) UnhandledPromiseRejectionWarning: PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x".

This is likely caused by a bundler that has not copied "libquery_engine-debian-openssl-3.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-debian-openssl-3.0.x.so.node" has been copied next to the bundle or in ".webpack/main".

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:
  /home/Projects/myelectron/.webpack/main
  /home/Projects/myelectron/.webpack
  /home/Projects/myelectron/node_modules/@prisma/client
  /home/Projects/.prisma/client
  /tmp/prisma-engines
    at ba (/home/Projects/myelectron/.webpack/main/index.js:299:805)
    at async Object.loadLibrary (/home/Projects/myelectron/.webpack/main/index.js:346:10020)
    at async xt.loadEngine (/home/Projects/myelectron/.webpack/main/index.js:347:448)
    at async xt.instantiateLibrary (/home/Projects/myelectron/.webpack/main/index.js:346:12630)

This can help us better understand where the engine was searched for

[totobest]

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

• I built the Next project from github actions (on ubuntu-latest worker) to get the Next static files.
• I run the project in Google App Engine, standard environment.

=> It seems both are not on the same os.

Solution:

• I rebuild the project in App Engine server

Alternative solution:

• Use Dockerfile to fix the OS and deploy to Cloud Run or any other container-aware host.

Which package manager are you using?
yarn 1.22.19

Is your workspace a monorepo setup?
single workspace

Is a bundler in use? If yes, which one?
Next/SWC

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

Your project uses TypeScript or just JavaScript?
Only TS

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

Where is your project deployed?
Google App Engine, standard runtime

Paste the error message

2024-04-20 22:38:53.699
GET
200
348 B
582 ms
Firefox 124.0
/api/auth/session
2024-04-20 22:38:54.199
�[31m[auth][error]�[0m AdapterError: Read more at https://errors.authjs.dev#adaptererror
2024-04-20 22:38:54.200
�[31m[auth][cause]�[0m: PrismaClientInitializationError:
2024-04-20 22:38:54.200
Invalid prisma.session.findUnique() invocation:
2024-04-20 22:38:54.200
Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x".
2024-04-20 22:38:54.200
This is likely caused by a bundler that has not copied "libquery_engine-debian-openssl-3.0.x.so.node" next to the resulting bundle.
2024-04-20 22:38:54.200
Ensure that "libquery_engine-debian-openssl-3.0.x.so.node" has been copied next to the bundle or in "src/generated/prisma".
2024-04-20 22:38:54.200
We would appreciate if you could take the time to share some information with us.
2024-04-20 22:38:54.200
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation
2024-04-20 22:38:54.200
The following locations have been searched:
2024-04-20 22:38:54.200
/workspace/src/generated/prisma
2024-04-20 22:38:54.200
/workspace/build/server
2024-04-20 22:38:54.200
/home/runner/work/trentiemeciel-newsletter/trentiemeciel-newsletter/src/generated/prisma
2024-04-20 22:38:54.200
/workspace/.prisma/client
2024-04-20 22:38:54.200
/tmp/prisma-engines
2024-04-20 22:38:54.200
at In.handleRequestError (/workspace/build/server/chunks/448.js:6750:39)
2024-04-20 22:38:54.200
at In.handleAndLogRequestError (/workspace/build/server/chunks/448.js:6702:18)
2024-04-20 22:38:54.200
at In.request (/workspace/build/server/chunks/448.js:6683:18)
2024-04-20 22:38:54.200
at async l (/workspace/build/server/chunks/448.js:7280:25)
2024-04-20 22:38:54.200
at async getSessionAndUser (/workspace/build/server/chunks/439.js:1367:36)
2024-04-20 22:38:54.200
at async acc. (/workspace/build/server/chunks/439.js:6658:24)
2024-04-20 22:38:54.200
at async session (/workspace/build/server/chunks/439.js:10879:30)
2024-04-20 22:38:54.200
at async AuthInternal (/workspace/build/server/chunks/439.js:11287:24)
2024-04-20 22:38:54.200
at async Auth (/workspace/build/server/chunks/439.js:11529:34)
2024-04-20 22:38:54.200
at async /layers/google.nodejs.yarn/yarn_modules/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:34754
2024-04-20 22:38:54.200
�[31m[auth][details]�[0m: {}
2024-04-20 22:38:54.201
�[31m[auth][error]�[0m SessionTokenError: Read more at https://errors.authjs.dev#sessiontokenerror

[dominoFire]

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?

I just tried first setting a output param in the schema file, then installing the nextjs monorepo workaround package

Which package manager are you using?

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

npm

Is your workspace a monorepo setup?

Is your setup hosting multiple packages in a single workspace?

Monorepo

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

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

webpack

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

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

Next.js

Your project uses TypeScript or just JavaScript?

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?

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

It happened in my deployed backend. I had to look at the logs in the cloud.

Where is your project deployed?

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

Firebase

Paste the error message

This can help us better understand where the engine was searched for

Edited logs from the cloud.

PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "debian-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-debian-openssl-3.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-debian-openssl-3.0.x.so.node" has been copied next to the bundle or in "prisma/generated".
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:
/workspace/prisma/generated
/workspace/.next/server
C:\src\propio3\lana\frontend\prisma\generated
/workspace/.prisma/client
/tmp/prisma-engines
at wa (/workspace/.next/server/chunks/297.js:64:756)
at async Object.loadLibrary (/workspace/.next/server/chunks/297.js:111:10014)
at async wt.loadEngine (/workspace/.next/server/chunks/297.js:112:448)
at async wt.instantiateLibrary (/workspace/.next/server/chunks/297.js:111:12734)
at async wt.start (/workspace/.next/server/chunks/297.js:112:1976)
at async wt.transaction (/workspace/.next/server/chunks/297.js:111:12027)
at async Proxy._transactionWithCallback (/workspace/.next/server/chunks/297.js:127:9313)
at async R (/workspace/.next/server/app/ext/api/partners/route.js:1:9224)
at async /workspace/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:34801
at async eS.execute (/workspace/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:25910) {
clientVersion: '5.15.0',
errorCode: undefined
}

⨯ Failed to load next.config.mjs, see more info here https://nextjs.org/docs/messages/next-config-error

Error: Dynamic require of "path" is not supported
    at file:///workspace/next.config.mjs:12:9
    at node_modules/@prisma/nextjs-monorepo-workaround-plugin/index.js (file:///workspace/next.config.mjs:37:16)
    at __require2 (file:///workspace/next.config.mjs:15:50)
    at file:///workspace/next.config.mjs:143:56
    at ModuleJob.run (node:internal/modules/esm/module_job:222:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
    at async loadConfig (/workspace/node_modules/next/dist/server/config.js:698:36)
    at async initialize (/workspace/node_modules/next/dist/server/lib/router-server.js:54:20)
    at async NextCustomServer.prepare (/workspace/node_modules/next/dist/server/next.js:242:28)
    at async Module.handle (file:///workspace/node_modules/firebase-frameworks/dist/next.js/index.js:13:5)

[ahardin13]

We get this error if we don't copy schema.prisma into the dist folder when deploying a service built with esbuild.

For reference, here's our client definition in /prisma/schema/schema.prisma. If we copy this file to dist before deploying, Prisma will use the correct binary.

generator client {
  provider        = "prisma-client-js"
  binaryTargets   = ["native", "rhel-openssl-1.0.x", "linux-arm64-openssl-1.1.x"]
  previewFeatures = ["views", "postgresqlExtensions", "prismaSchemaFolder"]
}

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

We are copying the engine we want to use, but prisma tries using a different one (see error message).

Which package manager are you using?

yarn 1.3

Is your workspace a monorepo setup?

Yes

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

esbuild in this case

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

No

Your project uses TypeScript or just JavaScript?

TypeScript?

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

In the deployment

Where is your project deployed?

Yes, in AWS Lambdas and ECS

Paste the error message

PrismaClientInitializationError:
Invalid `prisma.job.findMany()` invocation in
/usr/app/apps/[file path]/index.ts:48:33
45
46 async function runJobs() {
47 const prisma = await getClient();
→ 48 const jobs = await prisma.job.findMany(
Prisma Client could not locate the Query Engine for runtime "linux-arm64-openssl-1.1.x".
This is likely caused by a bundler that has not copied "libquery_engine-linux-arm64-openssl-1.1.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-linux-arm64-openssl-1.1.x.so.node" has been copied next to the bundle or in "../../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:
/node_modules/.prisma/client
/usr/app/apps/tasks/manager
/Users/ahardin/dev/[our_project]/node_modules/@prisma/client
/usr/app/apps/.prisma/client
/tmp/prisma-engines
at In.handleRequestError (/usr/app/node_modules/@prisma/client/runtime/library.js:122:7177)
at In.handleAndLogRequestError (/usr/app/node_modules/@prisma/client/runtime/library.js:122:6211)
at In.request (/usr/app/node_modules/@prisma/client/runtime/library.js:122:5919) {
clientVersion: '5.15.0',
errorCode: undefined
}

[ablomm]

I am trying to centralize the Prisma schema in a microservice-type application. I followed this article: https://medium.com/@nolawnchairs/sharing-prisma-between-multiple-applications-5c7a7d131519.

So I have one application called 'rapporto-prisma' and another appliaction called 'frontend' (which is a nextjs application). The 'rapporto-prisma' contains the prisma migrations and schema, and an index.js that simply re-exports the prisma client.

Everything is in a npm workspace, so 'frontend' can import from 'rapporto-prisma', but 'frontend' is not able to find the Query Engine. It searches the following locations:

<project path>/frontend/node_modules/.prisma/client
<project path>/frontend/.next/server
<project path>/common-libs/rapporto-prisma/node_modules/@prisma/client
<project path>/frontend/.prisma/client
/tmp/prisma-engines

I thought it was quite odd that it is searching common-libs/rapporto-prisma/node_modules/@prisma/client
but not common-libs/rapporto-prisma/node_modules/@prisma/engines, or common-libs/rapporto-prisma/node_modules/.prisma/client, both of which contain the correct engine file.

I copied the engine file from common-libs/rapporto-prisma/node_modules/.prisma/client to common-libs/rapporto-prisma/node_modules/@prisma/client and everything worked fine.

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

Yes, and it worked

Our error message suggested you to copy the engine somewhere. How did that go?
Which package manager are you using?

I just copied common-libs/rapporto-prisma/node_modules/.prisma/client to /common-libs/rapporto-prisma/node_modules/@prisma/client
I am using npm.

For instance npm, pnpm, or yarn. Please attach the version if you know it.
Is your workspace a monorepo setup?

version 10.7, yes monorepo

Is your setup hosting multiple packages in a single workspace?
Is a bundler in use? If yes, which one?

Yes there are multiple npm packages if that is what you are asking. Using whatever bundler nextjs uses (I think webpack)

Are you using webpack, swc, esbuild, rollup, or any other bundler?
Is a framework in use? If yes, which one?

nextjs

Are you using Next.js, Next, or any other framework?
Your project uses TypeScript or just JavaScript?

typescript

Do you prefer using TypeScript or JavaScript within your project, or both?
When you saw our message, did it happen locally or in deployment?

locally

The message was "Please help us by answering a few questions".
Where is your project deployed?

not deployed

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

no

[HelpfulScripts]

Have you tried to copy the engine in the suggested location? Did that work?
Yes. I am developing on an M2 Mac and deploying to an Intel Mac. I followed the instructions in the error message of the target machine, which gave me a clear understanding of the location to copy to. Many thanks for including that!. After copying, everything ran fine.

Which package manager are you using?
npm 10.2.3

Is your workspace a monorepo setup?
Yes

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

Is a framework in use? If yes, which one?
NextJS v14.2.5

Your project uses TypeScript or just JavaScript?
Typescript

When you saw our message, did it happen locally or in deployment?
in deployment on the target machine.

Where is your project deployed?
Intel Mac on the local network

Paste the error message
PrismaClientInitializationError:
Invalid prisma.account.findMany() invocation:

Prisma Client could not locate the Query Engine for runtime "darwin".

This is likely caused by a bundler that has not copied "libquery_engine-darwin.dylib.node" next to the resulting bundle.
Ensure that "libquery_engine-darwin.dylib.node" has been copied next to the bundle or in "app/...".

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:
/Users/...
/Users/...
/Users/...
/Users/...
/tmp/prisma-engines
/Users/
at _n.handleRequestError (/Users/.../.bin/server/chunks/3074.js:129:7945)
at _n.handleAndLogRequestError (/Users/.../.bin/server/chunks/3074.js:129:6969)
at _n.request (/Users/.../.bin/server/chunks/3074.js:129:6653)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async l (/Users/.../.bin/server/chunks/3074.js:138:9208)
at async Object.k [as ...] (/Users/.../.bin/server/chunks/3074.js:139:1855)
at async u (/Users/.../.bin/server/chunks/3074.js:9:7232)
at async /Users/.../node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:418
at async rP (/Users/.../node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:7978)
at async r5 (/Users/.../node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:18:1139) {
clientVersion: '5.17.0',
errorCode: undefined,
digest: '2026397136'
}

[danomatic]

Have you tried to copy the engine in the suggested location? Did that work?
I copied the engine to the same directory as the bundle, but it didn't work. I then copied it to the directory above (which is a strange place for it to live), and it worked.

Which package manager are you using?
Yarn 1.22.5

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?
Esbuild

Is a framework in use? If yes, which one?
Node 16, Fastify, Mercurius, Prisma

Your project uses TypeScript or just JavaScript?
TypeScript

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

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

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

Where is your project deployed?
Kubernetes via Jenkins

Paste the error message
It's no longer available

[rubenfiszel]

@danomatic same issue as you and created a PR to fix it: #24941

[WilliamBlais]

Have you tried to copy the engine in the suggested location? Did that work?
I tried to commit libquery_engine-rhel-openssl-3.0.x.so.node (added exception to gitignore) to /var/task/apps/tracker/.next/.prisma/client, same error message.

Which package manager are you using?
pnpm

Is your workspace a monorepo setup?
monorepo using Turbo

Is a bundler in use? If yes, which one?
Default next.js 14 bundler with @prisma/nextjs-monorepo-workaround-plugin plugin

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?
Only on a vercel production or preview deployment. Working totally fine locally.

Where is your project deployed?
Vercel

Paste the error message

Unhandled Rejection: PrismaClientInitializationError: 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/@prisma+client@5.18.0_prisma@5.18.0/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/@prisma+client@5.18.0_prisma@5.18.0/node_modules/.prisma/client
  /var/task/apps/tracker/.next/server/app
  /vercel/path0/node_modules/.pnpm/@prisma+client@5.18.0_prisma@5.18.0/node_modules/@prisma/client
  /var/task/apps/tracker/.next/.prisma/client
  /tmp/prisma-engines
    at va (/var/task/apps/tracker/.next/server/app/(dashboard)/page.js:214:756)
    at async Object.loadLibrary (/var/task/apps/tracker/.next/server/app/(dashboard)/page.js:261:10016)
    at async Tr.loadEngine (/var/task/apps/tracker/.next/server/app/(dashboard)/page.js:262:448)
    at async Tr.instantiateLibrary (/var/task/apps/tracker/.next/server/app/(dashboard)/page.js:261:12482) {
  clientVersion: '5.18.0',
  errorCode: undefined
}
Node.js process exited with exit status: 128. The logs above can help with debugging the issue.

My monorepo structure:

I tried two solutions:

• Using @prisma/nextjs-monorepo-workaround-plugin plugin and using a custom output to /packages/db/src/generated. Same error message.
• Having a duplicate prisma.schema on both apps/tracker and packages/db. Working, but very not ideal.

Note: It crashes while importing prisma on server actions.

[iamkoby]

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

Which package manager are you using?
Bun 1.1.26

Is your workspace a monorepo setup?
yes, turborepo

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

Is a framework in use? If yes, which one?
next.js 14 app router

Your project uses TypeScript or just JavaScript?
ts only

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

Where is your project deployed?
vercel

Paste the error message

PrismaClientInitializationError: 
Invalid `prisma.store.findUnique()` invocation:


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 "dist".

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/apps/store/dist
  /var/task/apps/store/.next/server
  /vercel/path0/packages/db/dist
  /var/task/apps/store/.prisma/client
  /tmp/prisma-engines
    at _n.handleRequestError (/var/task/apps/store/.next/server/chunks/377.js:121:7945)
    at _n.handleAndLogRequestError (/var/task/apps/store/.next/server/chunks/377.js:121:6969)
    at _n.request (/var/task/apps/store/.next/server/chunks/377.js:121:6653)
    at async a (/var/task/apps/store/.next/server/chunks/377.js:130:9208)
    at async /var/task/apps/store/.next/server/app/[domain]/l/[...details]/page.js:1:3316 {
  clientVersion: '5.18.0',
  errorCode: undefined,
  digest: '553103770'
}

[elvisdbl]

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

Which package manager are you using?
npm or yarn, mostly yarn

Is your workspace a monorepo setup?
mono

Is a bundler in use? If yes, which one?
i think i dont.

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

Your project uses TypeScript or just JavaScript?
Typescript

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

Where is your project deployed?
AWS LAMBDA

Hi, I recently created a new project using the new version of serverless (4) and I decided to use prisma as I usually do but when I run my sls comand to test a simple endpoint I get the following problem:

─ PrismaClientInitializationError: 
Invalid `prisma.product_type.findMany()` invocation:


Prisma Client could not locate the Query Engine for runtime "windows".

This is likely caused by a bundler that has not copied "query_engine-windows.dll.node" next to the resulting bundle.
Ensure that "query_engine-windows.dll.node" has been copied next to the bundle or in "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:
  C:\Users\elelv\Documents\Feedback\backend\.serverless\build\node_modules\.prisma\client
  C:\Users\elelv\Documents\Feedback\backend\.serverless\build\src\functions\product_type
  C:\Users\elelv\Documents\Feedback\snapapp-backend\node_modules\@prisma\client
  C:\Users\elelv\Documents\Feedback\backend\.serverless\build\src\.prisma\client
  /tmp/prisma-engines
    at Ln.handleRequestError (C:\Users\elelv\Documents\Feedback\backend\.serverless\build\src\functions\product_type\list\handler.js:4940:37)
    at Ln.handleAndLogRequestError (C:\Users\elelv\Documents\Feedback\backend\.serverless\build\src\functions\product_type\list\handler.js:4922:16)
    at Ln.request (C:\Users\elelv\Documents\Feedback\backend\.serverless\build\src\functions\product_type\list\handler.js:4913:16)
    at async l (C:\Users\elelv\Documents\Feedback\backend\.serverless\build\src\functions\product_type\list\handler.js:5306:21)
    at async handler (C:\Users\elelv\Documents\Feedback\backend\.serverless\build\src\functions\product_type\list\handler.js:5682:24)
    at async file:///C:/Users/elelv/.serverless/releases/4.3.3/package/lib/plugins/aws/dev/local-lambda/runtime-wrappers/node.js:167:24 {
  clientVersion: '5.19.1',
  errorCode: undefined
}
← λ product_type_list```

[Coltensiemer]

Have you tried to copy the engine in the suggested location? Did that work?
Yes and it does not work.

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

Is your workspace a monorepo setup?
Yes, it's a monorepo.

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

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?

On AWS lambda console.

The message was "Please help us by answering a few questions".
Where is your project deployed?

Amplify / AWS Lambda

"errorType": "PrismaClientInitializationError",
"errorMessage": "\nInvalid prisma.quiz.findMany() invocation:\n\n\nPrisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".\n\nThis is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" next to the resulting bundle.\nEnsure that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied next to the bundle or in "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-bundler-investigation\n\nThe following locations have been searched:\n /var/task/node_modules/.prisma/client\n /var\n /Users/coltensiemer/Documents/git-hub/AWS_Learn/node_modules/@prisma/client\n /.prisma/client\n /tmp/prisma-engines",
"trace": [
"PrismaClientInitializationError: ",
"Invalid prisma.quiz.findMany() invocation:",
"",
"",
"Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".",
"",
"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/.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/.prisma/client",
" /var",
" /Users/coltensiemer/Documents/git-hub/AWS_Learn/node_modules/@prisma/client",
" /.prisma/client",
" /tmp/prisma-engines",
" at Ln.handleRequestError (/var/task/index.js:4940:37)",
" at Ln.handleAndLogRequestError (/var/task/index.js:4922:16)",
" at Ln.request (/var/task/index.js:4913:16)",
" at async l (/var/task/index.js:5306:21)",
" at async getQuestions (/var/task/index.js:5734:19)"
]
}

This can help us better understand where the engine was searched for