Seems Prisma is failing for NodeJS 16.x

Bug description

Seems Prisma is failing for NodeJS 16.x. My tests and express js server using prisma are working fine for NodeJS 15.14.0 but start working once I update my node to 16.x

node[20990]: ../src/node_http_parser.cc:567:static void node::(anonymous namespace)::Parser::Initialize(const FunctionCallbackInfo<v8::Value> &): Assertion `args[3]->IsInt32()' failed.
 1: 0x106095ee5 node::Abort() (.cold.1) [/usr/local/bin/node]
 2: 0x104d4bdc9 node::Abort() [/usr/local/bin/node]
 3: 0x104d4bc31 node::Assert(node::AssertionInfo const&) [/usr/local/bin/node]
 4: 0x104d6906f node::(anonymous namespace)::Parser::Initialize(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node]
 5: 0x104f3cae5 v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo) [/usr/local/bin/node]
 6: 0x104f3c0b8 v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/usr/local/bin/node]
 7: 0x104f3b67f v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/usr/local/bin/node]
 8: 0x1057caa19 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_BuiltinExit [/usr/local/bin/node]
 9: 0x105765445 Builtins_InterpreterEntryTrampoline [/usr/local/bin/node]
[1]    20989 abort      npm run dev

How to reproduce

Expected behavior

Prisma information

Environment & setup

• OS: macOS Big Sur
• Database: PostgreSQL
• Node.js version: 16.x
• Prisma version:

╰─ npx prisma -v
Environment variables loaded from .env
prisma               : 2.21.2
@prisma/client       : 2.21.2
Current platform     : darwin
Query Engine         : query-engine e421996c87d5f3c8f7eeadd502d4ad402c89464d (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli e421996c87d5f3c8f7eeadd502d4ad402c89464d (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core e421996c87d5f3c8f7eeadd502d4ad402c89464d (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt e421996c87d5f3c8f7eeadd502d4ad402c89464d (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash : e421996c87d5f3c8f7eeadd502d4ad402c89464d
Studio               : 0.371.0

[pantharshit00]

@shirshak55 They are supported. But we do need to test when a node release happens and we fix these issues fairly quickly. Node 16 is fresh out of oven. The fix will be in the release next Tuesday.

[pinalbhatt]

Thanks @janpio

and yes @Jolg42 totally agree… my prod is running on LTS but I always run my tests in my ci/cd flow for LTS as well as latest version of nodejs.