"No X found" error thrown from a findUnique query does not show a stack trace #10641
Labels
bug/2-confirmed
Bug has been reproduced and confirmed.
kind/bug
A reported bug.
team/client
Issue for team Client.
topic: error
Milestone
Bug description
Error object thrown by prisma has no stack trace and message.
Stack trace and message should be available on all errors in node.js
when I call findUnique with
rejectOnNotFound
How to reproduce
Have a code like this:
Running this code using
ts-node pr.ts
prints out:Expected behavior
Stack trace in the error points into the line in user script where query was executed from.
For example an Error thrown should show up in stdout like this:
Prisma information
Environment & setup
Prisma Version
The text was updated successfully, but these errors were encountered: