-
Notifications
You must be signed in to change notification settings - Fork 2
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
exiting wiith error #6
Comments
Repo case:
@zilahir: |
Which version of npm 7 support was added in |
I was actually using the latest version (npm i npm-audit-helper@latest) of |
same here, i am also using the latest version! |
fun fact: it doesnt same to be working with script:
output
|
Related work: naugtur/npm-audit-resolver#34 |
Thanks so much for the error reports. I've implemented a quick fix I'd like to test. Would you mind please running: npm audit --json | npx [email protected] and let me know if that resolves the issue? You might notice the count of vulnerabilities is wrong, you can ignore that. If it does I'll clean it up and release it as a new |
Seems to be working fine: `❯ npm audit --json | npx [email protected] npm audit reportpostcss 7.0.0 - 8.2.9 43 moderate severity vulnerabilities To address all issues (including breaking changes), run: === A little bit of help === Where to start:
|
Thanks for checking @denisdanielyan. I've released the fix as |
unfortunately ths is still not working :( using npm 7+, with command:
and the result is:
Where |
Thanks @zilahir. That's a separate issue. Take a look at the docs – https://github.com/rouanw/npm-audit-helper#options. For npm 7, you can now tell "npm-test": "npm audit --json --only=prod | npm-audit-helper" |
This started to happen all of a sudden.
The script is the following:
this was working fine, but now:
I am using
npm 7 +
, and it seems like the format of the report json had been changed?If i am running the audit without the prod only flag:
It seems like ti's working, but i don't want to audit the
devDependencies
.Thanks!
The text was updated successfully, but these errors were encountered: