Keystone cli installs conflicting versions of prisma dependencies

[WoodyWoodsta]

Out of the box, keystone dev installs @prisma/client and prisma dependencies in such a way that version conflicts arise.

1. Perform "install" walkthrough
2. Run keystone dev

You'll see an error message which indicates a version mismatch of prisma dependencies:

Error: @prisma/client did not initialize yet. Please run "prisma generate" and try to import it again.

Expected:
Keystone works out of the box. Keystone CLI should install the packages locally with the same version specifier as its internal package.json.

Additional Info

$ pnpm why @prisma/client

dependencies:
@keystone-6/core 6.3.0
└── @prisma/client 5.19.0
@prisma/client 5.20.0

[gautamsi]

keystone has specific prisma version resolution, if you want to use higher version you want to add that to resolutions or overrides in your package.json

[WoodyWoodsta]

@gautamsi That is understood. However, the issue is that the keystone cli installs a version which does not match the specific version you mention.

[crewshin]

Ah... is this is why I'm having issues with a default/new install?

Literally you run:

pnpm create keystone-app@latest
cd my-app
pnpm run dev

and it errors out with:

Error: Schema engine exited. Error: Command failed with exit code 1: /Users/mee/src/tests/static/backend/node_modules/.pnpm/@prisma+engines@5.19.0/node_modules/@prisma/engines/schema-engine-darwin-arm64 cli --datasource <REDACTED> can-connect-to-database

[dwidge]

Workaround:
Check version: $ pnpm why @prisma/client.
Change version of prisma in 2 places in package.json to match version given above.

{
  "name": "keystone-app",
  "version": "1.0.3",
  "private": true,
  "scripts": {
    "dev": "keystone dev",
    "start": "keystone start",
    "build": "keystone build"
  },
  "dependencies": {
    "@keystone-6/auth": "^8.0.0",
    "@keystone-6/core": "^6.0.0",
    "@keystone-6/fields-document": "^9.0.0",
    "@prisma/client": "^5.22.0",
    "typescript": "^5.5.0"
  },
  "devDependencies": {
    "prisma": "^5.22.0"
  }
}

[dcousens]

@WoodyWoodsta how do you reproduce this problem?

[WoodyWoodsta]

@dcousens Repro is in the description:

1. Perform "install" walkthrough
2. Run keystone dev

I have not worked with this for quite some time so I'm not if it is still an issue.

[pxslip]

I have not worked with this for quite some time so I'm not if it is still an issue.

I'll chime in to say I just tried to spin up a fresh keystone install and ran into this issue.