You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some time GitHub checks the file package-lock.json to detect vulnerabilities - this course as it exists today results with the following diagnose (as a consequence of running npm install:
found 39 vulnerabilities (27 low, 3 moderate, 9 high) in 24102 scanned packages
run `npm audit fix` to fix 25 of them.
14 vulnerabilities require semver-major dependency updates.
I am proposing to update the file `package.json' to be:
Thanks for the info. I just run npm install
and it found 40 vulnerabilities. I ran npm audit fix
The console output after this was # Run npm install --save-dev [email protected] to resolve 12 vulnerabilities SEMVER WARNING: Recommended action is a potentially breaking change
I tested my luck by performing the recommended action. Works, no errors. I use Windows 10.
For some time GitHub checks the file package-lock.json to detect vulnerabilities - this course as it exists today results with the following diagnose (as a consequence of running
npm install
:I am proposing to update the file `package.json' to be:
After running the npm install with this
package.json
, run the following:This results with clean build - 0 vulnerabilities
The text was updated successfully, but these errors were encountered: