You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prisma version (prisma -v or npx prisma -v):
Studio version: Version 0.438.0 (0.438.0)
Logs from Developer Tools Console or Command line, if any:
TypeError: Do not know how to serialize a BigInt
at JSON.stringify (<anonymous>)
at new Tl (file:///Applications/Prisma%20Studio.app/Contents/Resources/app.asar/dist/renderer/assets/index.js:1:216912)
at bs (file:///Applications/Prisma%20Studio.app/Contents/Resources/app.asar/dist/renderer/assets/vendor.js:27:50128)
at Ha (file:///Applications/Prisma%20Studio.app/Contents/Resources/app.asar/dist/renderer/assets/vendor.js:27:67591)
at bl (file:///Applications/Prisma%20Studio.app/Contents/Resources/app.asar/dist/renderer/assets/vendor.js:27:105796)
at gu (file:///Applications/Prisma%20Studio.app/Contents/Resources/app.asar/dist/renderer/assets/vendor.js:27:97229)
at hu (file:///Applications/Prisma%20Studio.app/Contents/Resources/app.asar/dist/renderer/assets/vendor.js:27:97154)
at iu (file:///Applications/Prisma%20Studio.app/Contents/Resources/app.asar/dist/renderer/assets/vendor.js:27:94183)
at file:///Applications/Prisma%20Studio.app/Contents/Resources/app.asar/dist/renderer/assets/vendor.js:27:45779
at e.unstable_runWithPriority (file:///Applications/Prisma%20Studio.app/Contents/Resources/app.asar/dist/renderer/assets/vendor.js:18:3854)
Does the issue persist even after updating to the latest prisma alpha? (npm i -D @prisma/cli@dev)
yes
Prisma schema (if relevant):
model User {
id BigInt @id @default(autoincrement()) @db.BigInt
}
The text was updated successfully, but these errors were encountered:
@roncohen I think the person who originally opened that issue was on an old version of Prisma, but it looks like you're not. I will double-check to make sure this works
Prisma version (
prisma -v
ornpx prisma -v
):Studio version: Version 0.438.0 (0.438.0)
Logs from Developer Tools Console or Command line, if any:
Does the issue persist even after updating to the latest
prisma
alpha? (npm i -D @prisma/cli@dev
)yes
Prisma schema (if relevant):
The text was updated successfully, but these errors were encountered: