JSON.stringify is converting `Float` (`number`) values to strings.

Bug description

I’m using prisma with Typescript in a next.js application and JSON.strinfigy converts fields that are of type number (Float in the schema) to strings.

I did a little debugging and it looks like the Float fields are actually typeof 'object', not number, as I would have expected and what the generated @prisma/client types are telling me. The only thing I can think of is that Prisma is wrapping these values in something funky in the background?

For now my workaround is to do something like this:

export const toRaw = (user: User) => ({
  id: user.id,
  ...
  name: user.name,
  latitude: Number(user.latitude),
  longitude: Number(user.longitude),
});

How to reproduce

When I fetch and try to return json, latitude and longitude are being converted to strings:

const user = await prisma.user.findUnique({
  where: {
    id: req.user.id,
  },
});

JSON.stringify(user);

The output of which is:

{
  "name": "Super Dude",
  "longitude": "-118.235322", // <- STRING, not a number
  "latitude": "34.045148",  // <- STRING, not a number
}

Expected behavior

I’d expect the output to be:

{
  "name": "Super Dude",
  "longitude": -118.235322, // <- NUMBER, not a string
  "latitude": 34.045148,  // <- NUMBER, not a string
}

Prisma information

My schema for a User model is as follows:

// Schema
model User {
  id            String      @id @default(cuid())
  ...
  name          String?
  latitude      Float?
  longitude     Float?
}

// Generated type in @prisma/client
/**
 * Model User
 * 
 */
export type User = {
  id: string
  ...
  name: string | null
  latitude: number | null
  longitude: number | null
}

Environment & setup

Next.js with Typescript.

Prisma Version

prisma                  : 3.10.0
@prisma/client          : 3.10.0
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 73e60b76d394f8d37d8ebd1f8918c79029f0db86 (at node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Migration Engine        : migration-engine-cli 73e60b76d394f8d37d8ebd1f8918c79029f0db86 (at node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Introspection Engine    : introspection-core 73e60b76d394f8d37d8ebd1f8918c79029f0db86 (at node_modules/@prisma/engines/introspection-engine-debian-openssl-1.1.x)
Format Binary           : prisma-fmt 73e60b76d394f8d37d8ebd1f8918c79029f0db86 (at node_modules/@prisma/engines/prisma-fmt-debian-openssl-1.1.x)
Default Engines Hash    : 73e60b76d394f8d37d8ebd1f8918c79029f0db86
Studio                  : 0.458.0

[ifightcrime]

@janpio hey yes sorry I missed the first message! At the time I was a number of versions back too so who knows. I’m about to head out for the weekend though, but I will get back to you likely early next week.

[pantharshit00]

I am unable to reproduce this. I ran the query that you have posted and ran JSON.stringify to the result and output was correct:

I used Postgres as database? Can you please try again with latest version and possibly report which database are you using?

Edit: Tried again with the same values as you have specified and still got the correct result:

Script used:

import { PrismaClient } from "@prisma/client";

async function main() {
  const prisma = new PrismaClient();

  const user = await prisma.user.findUnique({
    where: {
      id: "cl11yqszv00072311gdwx6vo7",
    },
  });

  console.log(JSON.stringify(user));
  await prisma.$disconnect();
}

main();