Unable to run "keystone prisma migrate dev" from Turborepo monorepo

[stuible]

How to reproduce the bug

1. I created this repo with Turbo Repo's starter project by running:

npx create-turbo -e basic

2. I then added Keystone CMS to ~/apps/keystone using

cd apps
npm init keystone-app@latest keystone

3. I then modified the keystone package.json to have migrate script:

"migrate": "NODE_ENV=development keystone prisma migrate dev"

4. Move to keystone directory and run keystone command

cd apps/keystone # move to keystone directory
npm run migrate # run our new migrate npm command

5. Receive the following output:

Error: Prisma Migrate has detected that the environment is non-interactive, which is not supported.

Expected Result

I expect the migrations to be created through an interactive terminal

Context

• Node v18.18.0
• Turborepo

Repro Repo

https://github.com/stuible/keystone-interactive-cli-bug

Here is a MVP repo that reproduces the issue described above.

[austinbravodev]

I'm not using Turbo and the keystone prisma migrate dev command fails with the same error when run as an NPM script or via npx.

[flippinjoe]

This is actually a bug in turborepo. They swallow stdin (used for automatic migrations in keystone) vercel/turborepo#1235

[austinbravodev]

Could be both - I think the Keystone CLI creates a non-interactive context in which the Prisma command runs.

I'm just running it in my terminal, which should be interactive.

This would also explain why npx prisma migrate dev works.

[stuible]

This is actually a bug in turborepo. They swallow stdin (used for automatic migrations in keystone) vercel/turbo#1235

I have my doubts that this is a Turborepo issue because in the reproduction steps above I am bypassing the use of Turborepo completely (as far as I know).

[SagnikPradhan]

Weird, yarn keystone prisma migrate dev freezes but yarn dlx prisma@4.x migrate dev worked flawlessly

[stuible]

Weird, yarn keystone prisma migrate dev freezes but yarn dlx prisma@4.x migrate dev worked flawlessly

Exactly my experience as well (with the equivalent npx commands)

[dcousens]

Fixed in #8898, will be published soon