Replies: 1 comment 2 replies
-
Is it not printed when you click on the error? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
At the moment, the extension does not seem to provide support for Errors coming with an explicit cause. Here is what I get on VSCode at the moment when throwing such Error:
It would be awesome if Vitest extension could not only report the Error, but also its causes (possibly many). Some libraries such as fast-check makes intensive usage of the causes to wrap original errors (often linked to calls to
expect
) into library specific errors.If such feature makes sense and given enough pointers, I'd be happy to given an hand
Beta Was this translation helpful? Give feedback.
All reactions