node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.nodels: cannot access 'node_mod

[zealous elm]

I'm trying to deploy a Web Application to Azure using Node.js 20 and Prisma 6 through GitHub Actions. However, during the deployment process, I am encountering the following error:

node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
ls: cannot access 'node_mod

This error occurs when the process attempts to access the libquery_engine-debian-openssl-3.0.x.so.node file but cannot find the required file during deployment.

I have tried a few solutions, such as ensuring the Prisma client is generated before deployment, but the issue persists. Has anyone encountered this error in a similar environment and has any suggestions on how to resolve it? Could this be related to the Azure environment or Prisma configuration during deployment?

[willow ravine]

You decided to hold for human wisdom. We'll chime in soon! Meanwhile, #ask-ai is there if you need a quick second opinion.

[lost gazelle]

Hey 👋
Did you try specifying binary target like this in your prisma schema?

https://www.prisma.io/docs/orm/reference/prisma-schema-reference#linux-debian-x86_64

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