Jacob Coker-Dukowitz
04/19/2022, 10:11 PMdb/generated/client
when it should search in ./db/generated/client
:
I get a 'module not found' error when prisma tries to find my query engine binary here, which results in the 'Library may be corrupt' error defined below that line. However the engine is there - it looks like the path prisma is using to find the engine is wrong. Oddly this only occurs when working in a Docker image. Code runs fine locally. Here's where it looks:
prisma:client:libraryEngine Searching for Query Engine Library in db/.prisma/client +0ms
prisma:client:libraryEngine Searching for Query Engine Library in /Users/path/to/local/directory/my-service/db/generated/client +1ms
prisma:client:libraryEngine Searching for Query Engine Library in db/generated/client +0ms
When I add ./
in front of the path to resolve the engine as ./db/generated/client
, the code works.
Does the engine need to be located at the root, or is there something obvious I'm doing wrong?Jacob Coker-Dukowitz
04/19/2022, 10:11 PMgenerator client {
provider = "prisma-client-js"
output = "./generated/client"
binaryTargets = ["native", "linux-musl"]
}
Nurul
04/20/2022, 9:37 AMJacob Coker-Dukowitz
04/20/2022, 3:59 PM