JSON.stringify loses much of error object information vs using console.log on it

Bug description

We have a production service that uses prisma & catches an error thrown from prisma that looks like this:

{
  clientVersion: "3.4.1"
}

How to reproduce

This is the query that triggers the error to be thrown:

try{
const startDate = new Date(Date.now() - 24 * 60 * 60 * 1000);
const limit = 100;

const query = Prisma.sql`
  select url, count(*) as count
  from (
    select distinct "Status"."userIdStr", "Status".url
    from "Status"
    where "Status"."createdAt" > (to_timestamp(${startDate.getTime()} / 1000.0))
        and "Status".url is not null
    ) as distinct_user_url_statuses
  group by url
  having distinct_user_url_statuses.count > 1
  order by count desc  
  limit ${limit}
`;
const data = await prisma.$queryRaw<{ url: string; count: number }[]>(query);
} catch (error){
  // log error
}

Expected behavior

an error to be thrown with a message & code that can help me debug what’s going on

Prisma information

prisma & client 3.4.1

prisma.schema:

// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

model User {
  idStr String @id 
  name String?
  statuses Status[]
  follows Follow[] @relation("Follower")
  followers Follow[] @relation("Followee")
}

model Follow {
  id Int @id @default(autoincrement())
  userIdStr String
  user User @relation("Follower", fields: [userIdStr], references: [idStr])
  followeeIdStr String
  followee User @relation("Followee", fields: [followeeIdStr], references: [idStr])
  @@unique([userIdStr, followeeIdStr])
}

model Status {
  idStr String @id
  createdAt DateTime
  userIdStr String
  retweetCount Int @default(0)
  favoriteCount Int @default(0)
  user User? @relation(fields: [userIdStr], references: [idStr])
  url String?
  rawJson Json?
}

Environment & setup

• GCP Cloud Function
• Database: PostgreSQL 13
• Node.js version: node v14

Prisma Version

from my local dev environment which is not what’s running in the cloud/prod:

Environment variables loaded from .env
prisma                  : 3.4.1
@prisma/client          : 3.4.1
Current platform        : windows
Query Engine (Node-API) : libquery-engine 57771c0558568c7d08bd34c7248af5244ae16bd9 (at node_modules\@prisma\engines\query_engine-windows.dll.node)
Migration Engine        : migration-engine-cli 57771c0558568c7d08bd34c7248af5244ae16bd9 (at node_modules\@prisma\engines\migration-engine-windows.exe)
Introspection Engine    : introspection-core 57771c0558568c7d08bd34c7248af5244ae16bd9 (at node_modules\@prisma\engines\introspection-engine-windows.exe)
Format Binary           : prisma-fmt 57771c0558568c7d08bd34c7248af5244ae16bd9 (at node_modules\@prisma\engines\prisma-fmt-windows.exe)
Default Engines Hash    : 57771c0558568c7d08bd34c7248af5244ae16bd9
Studio                  : 0.438.0

[bablukpik]

When this would be fixed? I’m also getting the same thing instead of the proper error message. I’m using "@prisma/client": "^4.2.0"

[whytrno]

I get same error here, i try to use simple findUniqueOrThrow function like this

try{
        const user = await prisma.user.findUniqueOrThrow({
            where: {
                id: req.params.id
            }
        })
        res.status(200).json({
            data: user
        })
    }catch(error){
        res.status(400).json({
            data: error
        })
    }

i get res like this

   {
  "data": {
    "clientVersion": "4.5.0"
  }
}

but when i throw(error) or console.log(error), i got like this

Invalid `prisma.user.findUniqueOrThrow()` invocation:

{
  where: {
    id: '5'
        ~~~
  }
}

Argument id: Got invalid value '5' on prisma.findUniqueUser. Provided String, expected Int.

I know that error happend because parameter is not Integer, but its helpfull when its return to client maybe like this, error: Got invalid value '5' on prisma.findUniqueUser. Provided String, expected Int.