A lot of issues point back to the error undefined target="exit", this issue tracks reproducing and fixing that. After this we need to revisit all other issues that pose this error, to validate if they are fixed or if there is an underlying error consumed in Photon/QE land.
Reproduction: https://github.com/divyendu-test/photonjs-357
Related issues:
https://github.com/prisma/photonjs/issues/305
https://github.com/prisma/photonjs/issues/355
I'm investigating this. The datamodel errors seem to not be handled properly. I'll try to test with a custom error handling where I make the datamodel errors more in line with the rest.
For anyone who reads this: This is fixed in the latest alpha, please try it out by installing the latest alpha via npm install prisma2@alpha && npm install @prisma/photon@alpha.
I already tried my reproduction and it is not reproducible.
@divyenduz I can confirm that the current @alpha provided me a much better error message. Thanks!
I only see the console in the GraphQL UI playground though and its hard to read.
Should the errors be logging to the console running the server too? Or is a flag needed for that?
This should doable via https://github.com/prisma/prisma2/issues/686
Most helpful comment
For anyone who reads this: This is fixed in the latest alpha, please try it out by installing the latest alpha via
npm install prisma2@alpha && npm install @prisma/photon@alpha.I already tried my reproduction and it is not reproducible.