I am trying to use Prisma with yarn v3.2.1 with PnP and whenever I run

prisma migrate

, it always defaults to using NPM instead of Yarn, which causes

node_modules

to be created and the prisma client to be generated in there, rather than the path I gave it in the

schema.prisma

client output.

Hey Michael! We have a few known issues when using Yarn and PnP. I would take a look at the discussion in this existing issue to see if you can find a workaround. If not, adding your unique use case as a comment would be really valuable!