Use console.error for Prisma errors (#8722)

Co-authored-by: Daniel Cousens <dcousens@users.noreply.github.com>
keystonejs · Aug 13, 2023 · 98fbbeb · 98fbbeb
1 parent 9b22f96
commit 98fbbeb
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 2 deletions.
diff --git a/.changeset/more-errors-please.md b/.changeset/more-errors-please.md
@@ -0,0 +1,5 @@
+---
+'@keystone-6/core': minor
+---
+
+`KS_PRISMA_ERRORS` are now logged with `console.error` on the server
diff --git a/packages/core/src/lib/core/graphql-errors.ts b/packages/core/src/lib/core/graphql-errors.ts
@@ -6,7 +6,9 @@ export const userInputError = (msg: string) =>
 export const accessDeniedError = (msg: string) =>
   new GraphQLError(`Access denied: ${msg}`, { extensions: { code: 'KS_ACCESS_DENIED' } });
 
-export const prismaError = (err: Error) => {
+export function prismaError(err: Error) {
+  console.error(err);
+
   if ((err as any).code === undefined) {
     return new GraphQLError(`Prisma error`, {
       extensions: {
@@ -23,7 +25,7 @@ export const prismaError = (err: Error) => {
       prisma: { ...err },
     },
   });
-};
+}
 
 export const validationFailureError = (messages: string[]) => {
   const s = messages.map(m => `  - ${m}`).join('\n');