Prisma Client returns incompatible BigInt type for fields

Bug description

When we use JS BigInt feature from ES2020, TypeScript uses the lowercase bigint primitive type, just like number vs. Number:

However, Prisma Client returns BigInt interface, which is incompatible with that bigint type:

How to reproduce

Create a Prisma model with BigInt columns and use Prisma Client method like .findFirst() to get the data. Then try to assign to a property/variable of bigint primitive type.

Expected behavior

Prisma Client should return primitive bigint type, just like it do with string or number.

Prisma information

model reveal {
  operation_id      BigInt          @id
  fee               BigInt
}

Environment & setup

• OS: Ubuntu 20.04
• Database: PostgreSQL
• Node.js version: 15.8
• Prisma version:

prisma               : 2.17.0
@prisma/client       : 2.17.0
Current platform     : debian-openssl-1.1.x
Query Engine         : query-engine 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/query-engine-debian-openssl-1.1.x)
Migration Engine     : migration-engine-cli 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Introspection Engine : introspection-core 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/introspection-engine-debian-openssl-1.1.x)
Format Binary        : prisma-fmt 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/prisma-fmt-debian-openssl-1.1.x)
Studio               : 0.353.0
Preview Features     : orderByRelation

[rode093]

Facing same trouble with latest version of prisma. Older version is working good

[timsuchanek]

Thanks a lot for reporting 🙏 This issue is fixed in the latest dev version of @prisma/client. You can try it out with npm i @prisma/client@dev.

In case it’s not fixed for you - please let us know and we’ll reopen this issue!