Auto-disconnect

Right now users need to explicitly call await prisma.disconnect() at the end of their program otherwise the running Node process won’t terminate.

Ideally the Prisma Client (or more correctly: the used Prisma Query Engine) should automatically disconnect when the Node process is trying to terminate. This removes a lot of friction points and simplifies the usage of Prisma Client - especially when getting started - since users don’t need to call await prisma.disconnect() explicitly anymore.

[timsuchanek]

The assumption was, that if we start the Prisma process as a detached child process, Node.js still could properly exit, once the event loop is empty.

However, the problem is, that we still need to keep a stream to the process’ stderr and stdout open. These streams will still prevent the Node.js process from exiting.

We can revisit this topic once we have replaced the HTTP server with Neon bindings, as that will fundamentally change the interaction between Node.js and Rust for Prisma Client.

Issue for Neon Bindings: https://github.com/prisma/prisma/issues/767

[pantharshit00]

@meotimdihia This will be soon resolved via https://github.com/prisma/prisma/issues/4911 as then node can directly call rust function instead of spawning a binary process. It is close to completion and being released in preview so stay tuned.