Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error starting Prisma Client: { "message": "\n Error: spawn typegraphql-prisma ENOENT\n at notFoundError #730

Closed
yashmc3 opened this issue Jul 12, 2021 · 2 comments
Assignees
Labels
bug/0-unknown Bug is new, does not have information for reproduction or reproduction could not be confirmed. kind/bug A reported bug.
Milestone

Comments

@yashmc3
Copy link

yashmc3 commented Jul 12, 2021

  1. Prisma version (prisma -v or npx prisma -v):

  2. Logs from Developer Tools Console or Command line, if any:

Error starting Prisma Client: {
  "message": "\n    Error: spawn typegraphql-prisma ENOENT\n        at notFoundError (C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/node_modules/cross-spawn/lib/enoent.js:6:26)\n        at verifyENOENT (C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/node_modules/cross-spawn/lib/enoent.js:40:16)\n        at ChildProcess.cp.emit (C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/node_modules/cross-spawn/lib/enoent.js:27:25)",
  "stack": "AggregateError: \n    Error: spawn typegraphql-prisma ENOENT\n        at notFoundError (C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/node_modules/cross-spawn/lib/enoent.js:6:26)\n        at verifyENOENT (C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/node_modules/cross-spawn/lib/enoent.js:40:16)\n        at ChildProcess.cp.emit (C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/node_modules/cross-spawn/lib/enoent.js:27:25)\n    at next (C:\\Users\\c3controls\\AppData\\Local\\Programs\\@prismastudio-electron\\resources\\app.asar\\node_modules\\p-map\\index.js:43:14)\n    at C:\\Users\\c3controls\\AppData\\Local\\Programs\\@prismastudio-electron\\resources\\app.asar\\node_modules\\p-map\\index.js:59:6\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)"
}
Error: Error starting Prisma Client: {
  "message": "\n    Error: spawn typegraphql-prisma ENOENT\n        at notFoundError (C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/node_modules/cross-spawn/lib/enoent.js:6:26)\n        at verifyENOENT (C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/node_modules/cross-spawn/lib/enoent.js:40:16)\n        at ChildProcess.cp.emit (C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/node_modules/cross-spawn/lib/enoent.js:27:25)",
  "stack": "AggregateError: \n    Error: spawn typegraphql-prisma ENOENT\n        at notFoundError (C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/node_modules/cross-spawn/lib/enoent.js:6:26)\n        at verifyENOENT (C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/node_modules/cross-spawn/lib/enoent.js:40:16)\n        at ChildProcess.cp.emit (C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/node_modules/cross-spawn/lib/enoent.js:27:25)\n    at next (C:\\Users\\c3controls\\AppData\\Local\\Programs\\@prismastudio-electron\\resources\\app.asar\\node_modules\\p-map\\index.js:43:14)\n    at C:\\Users\\c3controls\\AppData\\Local\\Programs\\@prismastudio-electron\\resources\\app.asar\\node_modules\\p-map\\index.js:59:6\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)"
}
    at ki.init (file:///C:/Users/c3controls/AppData/Local/Programs/@prismastudio-electron/resources/app.asar/renderer/assets/index.js:1:103816)
  1. Does the issue persist even after updating to the latest prisma alpha? (npm i -D @prisma/cli@dev)

  2. Prisma schema (if relevant):


@sdnts
Copy link
Contributor

sdnts commented Jul 14, 2021

Hey @yashmc3 , thanks for reporting this. Could you show me the generators you have defined in your Prisma Schema?
I think this might be related to (or the same thing as) #720

@sdnts sdnts added bug/0-unknown Bug is new, does not have information for reproduction or reproduction could not be confirmed. kind/bug A reported bug. labels Jul 14, 2021
@sdnts sdnts added this to the 2.28.0 milestone Jul 15, 2021
@sdnts
Copy link
Contributor

sdnts commented Jul 15, 2021

Hey @yashmc3, I've just pushed out a dev version that should fix this. Could you try updating your Prisma CLI (and Client) version to 2.28.0-dev.5 and try again? (You can also just run npm i prisma@dev @prisma/client@dev)

Do note that dev versions are mostly meant for internal use, and might contain unannounced breaking changes, so I'd recommend sticking with a stable Prisma version for your app.

Let me know if this is still broken for you, and I'll reopen!

@sdnts sdnts closed this as completed Jul 15, 2021
@sdnts sdnts self-assigned this Jul 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/0-unknown Bug is new, does not have information for reproduction or reproduction could not be confirmed. kind/bug A reported bug.
Projects
None yet
Development

No branches or pull requests

2 participants