Prisma: @prisma/client initialized at wrong location with custom output in Yarn Workspaces

[enzoferey]

Problem

When installing dependencies via Yarn Workspaces with a custom output path for the @prisma/client, the empty client still gets generated at the default path.

Solution

It should generate the empty client at the specified output path.

[pantharshit00]

Can you please share your yarn workspace setup in a git repository? That will help us in triaging this issue.

[pantharshit00]

@enzoferey I am going to close this as its been 3 months now and there is no activity here.

Please reply if you want us to take another look.

[enzoferey]

Sorry for not coming back at you. I had a workaround in place when I opened the issue, we shipped the project with it and I didn't had to come back to it yet. Hopefully it will be indirectly fixed when upgrading versions in a couple of months. I will let you know if it's not the case.