Hi everyone! Nice to join this community. I’ve bee...
# orm-help
b
Hi everyone! Nice to join this community. I’ve been using Prisma for close to a year on a side project with a few other developers, but as of this week, all of us are running into errors like
Query engine binary for current platform "linux-arm-openssl-1.1.x" could not be found.
Would really appreciate any help debugging this! I’ll drop more details into a 🧵
Of note, our repo is structured like:
web/server/package.json
web/server/node_modules/...
web/server/prisma/schema.prisma
web/server/.dist/index.js
<- where we compile code to We just switched over to using esbuild instead of typescript directly. But I haven’t noticed a connection between esbuild & this bug yet.
We use
yarn
for our package management.
prisma -v
Copy code
Environment variables loaded from .env
prisma               : 2.26.0
@prisma/client       : 2.26.0
Current platform     : darwin
Query Engine         : query-engine 9b816b3aa13cc270074f172f30d6eda8a8ce867d (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli 9b816b3aa13cc270074f172f30d6eda8a8ce867d (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 9b816b3aa13cc270074f172f30d6eda8a8ce867d (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt 9b816b3aa13cc270074f172f30d6eda8a8ce867d (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash : 9b816b3aa13cc270074f172f30d6eda8a8ce867d
Studio               : 0.408.0
Our team has tried running in a debian docker instance, on an intel mac, and on an m1 mac. All have been failing with similar error messages.
j
There could indeed be a connection to switchting to esbuild - the file missing often happens in the build process
Can you create a reproduction of your setup and share it as a Git repo on Github?
That would be easiest for us to look into.
b
I’ll try to create a simple repro and share. I was able to figure out a workaround though by going through many similar Github issues - copying the query engine, schema.prisma, and .env files into the
.dist
directory works perfectly! Of course, it’d be nice for this postbuild step to not be necessary though. I’ll post back here once I have a simple repro to share 🙂
j
Yeah that is also a big smell on our side if that is necessary. It really should not be - but build processes are the source of all evil 👿 😛