Constantly reoccuring "@prisma/client did not initialize yet."

[mandymozart]

I run into the same frustrating error whenever I start over setting up the project in a new instance.

I generate the prisma client with the postinstall routine and yarn. so basically that should work out of the box.

the post install tells me prisma client is now available at @prisma/client, which is exactly where it should be in the node modules folder.

yet, when I run keystone:dev the client can not be found, because keystone is looking for it in `node_modules/keystone-6/node_modules/'

only downgrading to @prisma/client 5.00.0 worked but only after up and downgrading. not exactly sure how to reproduce this "hack"

when I start fresh now i get this:

warn Versions of prisma@5.15.1 and @prisma/client@5.0.0 don't match.
This might lead to unexpected behavior.
Please make sure they have the same version.

and client once again can not be found. why the hell are there two @prisma/client?

here is my package:

{
  "name": "vibesss",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "keystone:dev": "dotenvx run -- keystone dev",
    "keystone:start": "dotenvx run -- keystone start",
    "keystone:build": "dotenvx run -- keystone build",
    "keystone:postinstall": "keystone build --no-ui --frozen",
    "next:dev": "node server.mjs",
    "next:build": "NODE_ENV=production next build",
    "next:start": "NODE_ENV=production node server.mjs",
    "postinstall": "prisma generate && keystone postinstall"
  },
  "dependencies": {
    "@apollo/client": "^3.10.6",
    "@apollo/experimental-nextjs-app-support": "^0.11.2",
    "@dotenvx/dotenvx": "^0.45.0",
    "@emotion/css": "^11.11.2",
    "@emotion/react": "^11.11.4",
    "@emotion/styled": "^11.11.5",
    "@keystone-6/auth": "^7.0.0",
    "@keystone-6/core": "^5.0.0",
    "@keystone-6/document-renderer": "^1.1.2",
    "@keystone-6/fields-document": "^7.0.0",
    "@prisma/client": "5.00.0",
    "clsx": "^2.1.1",
    "dayjs": "^1.11.11",
    "dotenv": "^16.4.5",
    "framer-motion": "^11.2.6",
    "graphql": "16.8.1",
    "graphql-request": "^7.1.0",
    "graphql-yoga": "^5.4.0",
    "http-proxy-middleware": "^3.0.0",
    "json-edit-react": "^1.11.0",
    "lodash": "^4.17.21",
    "nanoid": "^5.0.7",
    "next": "^14.2.4",
    "opensheetmusicdisplay": "^1.8.8",
    "osmd-audio-player": "^0.7.0",
    "p5": "^1.9.4",
    "react": "^18.3.1",
    "react-dom": "^18.3.1",
    "react-hot-toast": "^2.4.1",
    "react-icons": "^5.2.1",
    "react-input-position": "^1.3.2",
    "react-midi-context": "^1.0.20",
    "react-p5": "^1.4.1",
    "react-toggle": "^4.1.3",
    "react-touch-position": "^2.0.2",
    "simple-zustand-devtools": "^1.1.0",
    "socket.io": "^4.7.5",
    "socket.io-client": "^4.7.5",
    "typescript": "^4.9.5",
    "unique-names-generator": "^4.7.1",
    "use-mobile-detect-hook": "^1.0.5",
    "usehooks-ts": "^3.1.0",
    "zustand": "^4.5.2"
  },
  "devDependencies": {
    "prisma": "^5.15.1",
    "syncpack": "^12.3.2"
  },
  "resolutions": {
    "graphql": "16.8.1"
  },
  "engines": {
    "node": ">=18.0.0 <19.0.0"
  }
}

[mandymozart]

I found out how I inherited the version conflict. It is important to use the same fixed version number of prisma and @prisma/client. After I upgraded both to version 5.17.0 it works a bit better. I am still not able to make it work flawlessly or deploy a version of the UI on render.com but it's getting more easy to start the keystone:dev routine.