Prisma client won't generate and reports mismatch after upgrade to v4.5.0

Bug description

I was updating packages, I updated Prisma from v4.4.0 -> v4.5.0 Then, I used prisma generate and the generated client stopped working, and it says there is a prisma version mismatch (prisma = 4.5.0 vs @prisma/client = 4.4.0, even though when I run prisma --version it shows both are at 4.5.0).

I tried clearing my node modules and reinstalling, but after that didn’t work I tried clearing my pnpm store and reinstalling, but that didn’t work either.

I tried downgrading to v4.4.0, which didn’t work either.

I’m running a turbo repo and cleared the node_modules in all locations, and reinstalled using the above method.

How to reproduce

1. use pnpm prisma generate after updating from 4.4.0
2. attempt to import types or make queries
3. see error image

Expected behavior

Prisma client is generated correctly and able to be used.

Prisma information

Environment & setup

• OS: Fedora
• Database: MySQL (planetscale)
• Node.js version: v16.14.0

Prisma Version

[wladiston]

Having the same issue with NPM on a turborepo. Had to clean cache, remove all node_modules folders, pin 4.4.0 version and removed any reference to prisma from the package-lock to make it work.

Apparently 4.5.0 is installing under the package’s node_module folder as oppose to 4.4.0 that installs under the root node_modules.

If I just change to 4.4.0 on the package.json, it somehow keeps installing the 4.5.0 because there’s still some reference on the package-lock to it.

[Jolg42]

Hi @macklinhrw This is weird 🤔 Which version of pnpm are you using? What are the entries for prisma and @prisma/client in your package.json?