Issues With Prisma Return types

I have really dug deep to try and find a solution online before coming here but I really can't find anything. I'm seeing an issue where the return types I get back from calling prisma are not showing the actual model type, but instead showing this strange 'GetResult' type. Has anyone encountered this before? Again apologies if this is a low brow question I truly could not find anything online when searching GetResult type and prisma.

Screen_Shot_2023-07-13_at_10.04.42_AM.png

Lopen•7/13/23, 4:24 PM

Did you try regenerating the types and restarting ur ts server/vs code

Gabriel•7/13/23, 5:00 PM

I get this all the time as well. But I think this just resolves to the actual type you need later?

Gabriel•7/13/23, 5:01 PM

Did you try to call this from your frontend to see how the type gets infered/

Gabriel•7/13/23, 5:01 PM

Or try using RouterOutputs

lucaggOP•7/13/23, 5:18 PM

@lopen3 hey thank you so much for the response, greatly appreciated. Yep I have tried regenerating the prisma types, restarting my ts server and vs code. I even messed with the Tsserver: Use Syntax Server setting (changing it from auto to always) but the only impact that had was making everything type any lol. Again thank you for responding.

Lopen•7/13/23, 5:20 PM

Try typing it manually then

Lopen•7/13/23, 5:20 PM

Const test: type = ....

Lopen•7/13/23, 5:21 PM

You can import the typw from prisma client

lucaggOP•7/13/23, 5:24 PM

so I gave that a shot and what I'm noticing now is that the type that im importing from prisma actually has the strange GetResult wrapper...so maybe an issue with my schema.prisma file...hmmmm

Screen_Shot_2023-07-13_at_1.23.45_PM.png

Lopen•7/13/23, 5:31 PM

Trying creating an actual data

Lopen•7/13/23, 5:32 PM

Like make a new modal and run the migration and then try it on the new model

lucaggOP•7/13/23, 5:49 PM

okay sounds good, thanks again

lucaggOP•7/13/23, 5:54 PM

damn so i made this, ran npx prisma db push, but same result when importing it into the server the type is: (alias) type TestModel = runtime.GetResult<{
id: string;
howdy: string;
}, unknown> & {}
import TestModel

Screen_Shot_2023-07-13_at_1.53.36_PM.png

Lopen•7/13/23, 5:56 PM

Try

npx prisma generate

npx prisma generate

Lopen•7/13/23, 5:58 PM

Or try deleting your node modules folder and do fresh install

lucaggOP•7/13/23, 6:12 PM

damn so i tried running that. Then i tried deleting the node modules and running yarn and then npx prisma generate, then i tried the reverse deleting the node modules then running npx prisma generate and then yarn. All returned the same result, Its strange though because using an old t3 project i have on my lapot i can copy my code into there and the types are correct, but if i spin up a new t3 project and drop this same code in there it has the same problem....

Gabriel•7/15/23, 4:40 PM

Hey

Gabriel•7/15/23, 4:40 PM

I am having this same issue!

Gabriel•7/15/23, 4:40 PM

Is this maybe related to Prisma V.5?

Lopen•7/15/23, 6:12 PM

Try v4 or previous version

RozyB•7/15/23, 7:42 PM

I have the same issue using Prisma 4.16.24.16.2

Awot•12/10/23, 4:19 PM

I know this is an old thread but I had the same issue, downgrading seems to have fixed it for me. Even tho its not a good solution, it seems like its my only. Didnt test a lot with different versions but it seems like: pnpm up --save-exact prisma@4.15.0 @prisma/client@4.15.0pnpm up --save-exact prisma@4.15.0 @prisma/client@4.15.0 worked for me

Issues With Prisma Return types

Similar Threads

Similar Threads

Similar Threads