-
Notifications
You must be signed in to change notification settings - Fork 33
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
The 2.1.2
version is fails the audit
#23
Comments
Hi @hadaabhi201, I think these issues with If you are able to provide Pull Request with packages updates it would be great. |
Same here, I am getting issue with |
Ha, so it's not the problem with my OS. I'm having the same issue. Funny. OK, let's wait for the issue to be solved. |
All issues are fixed in version |
Repro Steps:
Node version:
v12.12.0
$ npm init -y
$ npm install --save chromium
Step 1. Retrieving Chromium latest revision number
Step 2. Downloading Chromium (this might take a while). Revision number: 751348
Step 3. Setting up Chromium binaries
Process is successfully finished
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN [email protected] No description
npm WARN [email protected] No repository field.
added 45 packages from 23 contributors and audited 48 packages in 12.252s
found 1 moderate severity vulnerability
run
npm audit fix
to fix them, ornpm audit
for detailsExpected:
Actual
The text was updated successfully, but these errors were encountered: