-
Notifications
You must be signed in to change notification settings - Fork 27
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
fix: 1 critical
vulnerability
#417
fix: 1 critical
vulnerability
#417
Conversation
Without this change
|
With this change
|
Too many changes with no clear context. Please explain in PR description what problem exactly we have, why and how this changes fix a problem. |
I updated the pull request description. Let me if there's anything else I can do to clarify things. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes here are just a result of running npm audit fix
.
fixes #416.
Problem
Several dependencies have issues. #416 (comment) has more details.
How this pull request fixes the problem
This pull request resolves the vulnerabilities that are easier to fix by updating
package-lock.json
.