Prisma Client crashes with Node.js 16.0.0

Bug description

This error actually comes from our dependency undici and was patched in 3.3.5 https://github.com/nodejs/undici/issues/753

Note: it’s not yet recommended to use Node 16 because LTS start date is for the end of the year 2021-10-26

 $ ts-node ./script.ts
/opt/hostedtoolcache/node/16.0.0/x64/bin/node[2518]: ../src/node_http_parser.cc:567:static void node::{anonymous}::Parser::Initialize(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[3]->IsInt32()' failed.
 1: 0xb12b00 node::Abort() [/opt/hostedtoolcache/node/16.0.0/x64/bin/node]
 2: 0xb12b7e  [/opt/hostedtoolcache/node/16.0.0/x64/bin/node]
 3: 0xb2a282  [/opt/hostedtoolcache/node/16.0.0/x64/bin/node]
 4: 0xd5f70b  [/opt/hostedtoolcache/node/16.0.0/x64/bin/node]
 5: 0xd60bac  [/opt/hostedtoolcache/node/16.0.0/x64/bin/node]
 6: 0xd61226 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [/opt/hostedtoolcache/node/16.0.0/x64/bin/node]
 7: 0x160c579  [/opt/hostedtoolcache/node/16.0.0/x64/bin/node]
Aborted (core dumped)
error Command failed with exit code 134.

How to reproduce

Install Node 16 and use Prisma Client

Expected behavior

No crash.

Environment & setup

• OS: Ubuntu
• Database: any
• Node.js version: 16
• Prisma version: latest dev

[Jolg42]

Hi @dickfickling

We do not plan to patch 2.21 with this fix at the moment since Node v16.0.0 just got out and is not recommended to use for production.

Our dev version 2.22.0-dev.25 or dev can be used to try things out if needed. Important to consider: we may break things and introduce unstable changes/features without warnings in the dev versions, so I would not recommend using it in production.

The next Prisma version, 2.22 will have the fix.

[Jolg42]

Confirmed working with 2.22.0-dev.25 in e2e test.

We recommend staying on latest Node.js LTS version (Node 14).

Next Prisma version 2.22.0 will include this fix, the release is planned on May 4th.