-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Yarn PNP errors are swallowed by Jest which makes debugging quite hard #9594
Comments
Thanks! In addition to surfacing that message about missing declared dependencies, we should also construct a |
@SimenB mind if I take this one? I've been digging into the source code and I have an idea of how to implement this, and a e2e test in place for it. |
Please do! |
Closed via #9681 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Original issue: yarnpkg/berry#943
In short, if some package has unlisted peer dependency, Jest will emit something like this (in this case it was
react-router@3
and it's underlying packagecreate-react-class
:As you see, there is no information to trace the error.
True error looks like this (
PNP_DEBUG_LEVEL=1
was set in environment):As you can see, the true error is:
The text was updated successfully, but these errors were encountered: