Since v2.4 prisma generate no longer works in yarn workspaces

Bug description

Running prisma generate within yarn workspaces fails with the error:

Running this command will add the dependency to the workspace root rather than the workspace itself,
which might not be what you want - if you really meant it, make it explicit by running this command 
again with the -W flag (or --ignore-workspace-root-check).

How to reproduce

1. Set up yarn workspaces in your repo
2. Set up prisma 2.4 (with prisma folder at root)
3. npx prisma generate

Expected behavior

The prisma types should be generated successfully.

Environment & setup

• OS: Mac OS
• Database: PostgreSQL
• Node.js version: 14.4
• Prisma version: 2.4

[marvinroger]

@pantharshit00 Yes, I am not saying it’s a bug, it’s just confusing in this edge case: initially, my project wasn’t in a monorepo setup, and everything was fine, because I had @prisma/cli installed in the only package I had. I forgot to install @prisma/client, but it was not problematic, because, as you said, the CLI installs the client automatically.

However, when I splitted my code as multiple packages, I installed @prisma/cli in the workspace root, and running prisma generate failed with the same error as OP. I think the CLI should warn us if @prisma/client is not installed, instead of trying to install automatically when ran in a monorepo root - which will fail.

[marvinroger]

This happens when you don’t have @prisma/client in your dependencies. Adding the dependency fixes the issue!