Prisma Client: Query Engine engineType=binary incompatible with Node.js v17? #9903
Description
Note: Node.js v17 is an intermediary release and won't become an LTS version and should not be used for production workloads.
I created a PR in our e2e tests suite here prisma/ecosystem-tests#2137 to add a minimal test for v17 which succeeds on engineType "library" but fails on "binary" with
https://github.com/prisma/e2e-tests/runs/3973259270?check_suite_focus=true#step:6:375
$ ts-node ./script.ts
PrismaClientKnownRequestError:
Invalid `client.user.deleteMany()` invocation in
/home/runner/work/e2e-tests/e2e-tests/generic/basic/script.ts:7:21
4
5 // A `main` function so that we can use async/await
6 async function main() {
→ 7 await client.user.deleteMany(
connect ECONNREFUSED ::1:43951
at cb (/home/runner/work/e2e-tests/e2e-tests/generic/basic/node_modules/@prisma/client/runtime/index.js:38537:17)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
code: 'ECONNREFUSED',
clientVersion: '3.4.0-dev.10',
meta: undefined
}
Rerunning the test results in the same error.
We should reproduce locally and see what's happening here, looks like something about IPv6 maybe? ECONNREFUSED ::1:43951
Node.js v17 changelog here (didn't find anything related) https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V17.md