Using Prisma with pnpm results in inability to call database related commands

[lamaqdahodwala]

Bug description

I am using pnpm with Prisma in my app, but whenever I try running prisma migrate dev or prisma generate, the program hangs for about 10 minutes before returning an error.

Running generate... (Use --skip-generate to skip the generators)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @eslint/eslintrc@2.0.0
npm WARN Found: peer eslint-plugin-jsdoc@">=22.1.0" from eslint-config-eslint@7.0.0
npm WARN node_modules/.pnpm/@eslint+eslintrc@2.0.0/node_modules/@eslint/eslintrc/node_modules/eslint-config-eslint
npm WARN   dev eslint-config-eslint@"^7.0.0" from @eslint/eslintrc@2.0.0
npm WARN   node_modules/.pnpm/@eslint+eslintrc@2.0.0/node_modules/@eslint/eslintrc
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer eslint-plugin-jsdoc@">=22.1.0" from eslint-config-eslint@7.0.0
npm WARN node_modules/.pnpm/@eslint+eslintrc@2.0.0/node_modules/@eslint/eslintrc/node_modules/eslint-config-eslint
npm WARN   dev eslint-config-eslint@"^7.0.0" from @eslint/eslintrc@2.0.0
npm WARN   node_modules/.pnpm/@eslint+eslintrc@2.0.0/node_modules/@eslint/eslintrc
npm ERR! Cannot read properties of null (reading 'matches')

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-03-06T21_07_48_240Z-debug-0.log
Error: Command failed with exit code 1: npm install @prisma/client@4.11.0

How to reproduce

1. Install Prisma using pnpm
2. Write some models in the Prisma schema
3. Run pnpm prisma migrate dev or pnpm prisma generate

Expected behavior

I expected Prisma to play nicely with the pnpm format, but it didn't. It seems like the problem might be a mismatch between the usage of pnpm and npm when installing @prisma/client, because even on my pnpm project, it still says that npm install @prisma/client was used.

Prisma information

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "sqlite"
  url      = env("DATABASE_URL")
}

model User {
  id Int @id @default(autoincrement())
  username String @unique
  password String
  
}

Environment & setup

• OS: WSL
• Database: SQLite
• Node.js version: 18.12.1

Prisma Version

4.11.0

[ghost]

I had the same issue. Good catch on spotting how @prisma/client was installed. After manually adding the package through pnpm (pnpm add @prisma/client) everything works again. pnpm prisma generate takes barely a second and generates a new Prisma Client as intended.

https://www.prisma.io/docs/reference/api-reference/command-reference#generate

The documentation does mention that prisma generate will install the @prisma/client package if not already present:

Installs the @prisma/client into the npm project if it is not already present.

TL;DR: pnpm add @prisma/client will fix this.

[tobychidi]

Ran into this issue for the first time today. I feel I have been using pnpm and prisma before without issues?

[millsp]

Hey folks, we have just improved our pnpm detection logic to fix this issue, and we will release this in our 4.13.0 release. That said, you can try it now by installing our dev version. npm install prisma@dev. Feedback welcome!

[mertcankurt]

Hello, this issue seems to have returned with version 5.7.0. When i install prisma with pnpm, @prisma/client is not installed. Could you check the issue when you are available ?

[millsp]

Hey @mertcankurt, could you please open a new issue and give us more details about your setup, and maybe a small repro?