question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Prisma Client not finding query-engine after electron packages everything

See original GitHub issue

So im making a project using electron and prisma (within others that we dont have to worry about) and i am trying to solve this error for hours, i cant get prisma to find the query-engine executable, and i’ve tried a BUNCH of things i found on internet but still nothing.

here is me trying to set where prisma will find the query-engine (i found this “solution”(at least not for me) at https://github.com/prisma/prisma/discussions/5200) image

this is my prisma schema image

i am using webpack to compile both electron and react, so i set the schema generate to the electron folder that webpack will then compile to the “dist” folder, i used the copy-webpack-plugin to copy both schema.prisma and the query-engine-windows.exe (wich is my os) and after all that i get this error :

image

event using this setup to get the app path and setting the path exactly where the qe (query-engine) is it says its not there…??

image

and to make sure i wasnt crazy i took the path it said it wanst there and threw it to the console and it ran!!! so something is wrong here.

this is the output for this QE path change :

image

if u have some questions about how some files look u can check at my repo this project repo

if u want to get the error and try out urself to get the error just clone the repo, do yarn and run “yarn package:exe” wich will compile the main folder wich is electron and then the src folder wich is react and right after that it will bundle it for electron and then execute it right away,

  • yarn package:exe will webpack-(all)>electron->execute thanks for reading everything 👍 hope u can help me 💯 . If u need any more details just ask for them, Thanks in advance.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:11 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
Tiago-0liveiracommented, Jul 6, 2021

Sure! I completely understand but i just really wanted to have someone tell me something about it, i mean this kind of message u just sent me, at least now i know i probably wont have an answer so soon. Thanks!

0reactions
garrensmithcommented, Aug 22, 2022

@Tiago-0liveira could you try again? We fixed a bug in our __internal.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Prisma Client not finding query-engine after electron ...
I've never worked with prisma or electron, but based on my webpack experience there are few things that sound very off:.
Read more >
Can not spawn Query Engine when using Electron · Issue #9619 ...
However in order to spawn the Query Engine binary, it has to be outside the ASAR ... Since 3.x Prisma Client uses a...
Read more >
Prisma CLI Command Reference
This page gives an overview of all available Prisma CLI commands, explains their options and shows numerous usage examples.
Read more >
Prisma Client
Prisma Client is an auto-generated, type-safe query builder generated based ... the client to pass all the queries on to the query engine...
Read more >
Deploying to a different OS - Prisma
The query engine is implemented in Rust and is used by Prisma in the form of executable binary files. The binary is downloaded...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found