I have no idea where the `@prisma/client@2.20.1` i...
# orm-help
j
I have no idea where the
@prisma/client@2.20.1
is coming from šŸ¤”
e
What does
yarn list @prisma/client
give you šŸ™‚ ?
j
I think I pinpointed the issue
Copy code
[prisma:codegen] āœ” Generated Prisma Client (2.20.1) to ./cdk.out/asset.d85473858cfed0fe9f8aeebd3e4a53f213d1dcf518eb992e4ba358bdd8327b44/nodejs/node_modules/@prisma/client in 643ms
Seems like prisma is generating the client in my cdk cache folder oO
After deleting the cdk.out folder :
Copy code
[prisma:codegen] āœ” Generated Prisma Client (2.25.0) to ./../../node_modules/@prisma/client in 391ms
Something is definitly off about the location detection
j
How did you get into that situation?
Do you still have a project where you can reproduce this? If so, an issue would be nice.
Somehow it is really bad at detecting the correct location here.
j
I don’t have the folder anymore but I think I could setup a repro
basically I’m in a monorepo with yarn v1
so prisma is located in the root node_modules, and used/declared in the package.json of my ./packages/server
in ./packages/server I also use aws cdk which do some bundling before deploying in a temporary folder at ./packages/server/.cdk.out
my prisma config is located at ./packages/server/prisma/schema.prisma
and the ā€œprisma generateā€ command is located in my ./packages/server/package.json file as a script command
I have no idea why prisma is diving in cdk.out, I would think it try to apply node_modules resolution algorithm
here it’s diving into a sibling directory? ^^'
j
That would also be my question šŸ˜›
So if you get to a repro, super happy to get someone to look into it and understand.
We have quite a few problems with this logic recently after we slightly chanegd it, so this might be connected as well.