-
Notifications
You must be signed in to change notification settings - Fork 43
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
Handle errors from Yarn Berry more gracefully #301
Labels
Comments
I am pretty sure this is the case for all package managers. Since every package manager implementation attempts to Perhaps we just wrap all |
quinnturner
added a commit
to quinnturner/audit-ci
that referenced
this issue
Jan 13, 2023
quinnturner
added a commit
to quinnturner/audit-ci
that referenced
this issue
Jan 13, 2023
Signed-off-by: Quinn Turner <[email protected]>
quinnturner
added a commit
to quinnturner/audit-ci
that referenced
this issue
Jan 13, 2023
Signed-off-by: Quinn Turner <[email protected]>
quinnturner
added a commit
that referenced
this issue
Jan 23, 2023
Merged
Closed with #306, released in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, if
yarn npm audit
has some error (other than detected vulns),audit-ci
with fail with an error like this:Instead, audit-ci's thrown error message should probably include some info about the error Yarn reported.
I ran into this in #298 , and also when trying to bump the tested Yarn version in PR #300 (CI link here)
The text was updated successfully, but these errors were encountered: