Problem

If there is a typo/misuse in Prisma client's constructor parameters. We silently get a Prisma client object.

Suggested solution

It should fail with a runtime validation error like queries fail.

Additional context

I ran into this multiple time when using Prisma client in Javascript where I had either a typo or I was inadvertently using a param that didn't exist.