fix current packages with vulnerability#648
Conversation
Signed-off-by: Rafael Camara <rafaelcamarac@gmail.com>
e2c3d09 to
451f39f
Compare
mikeee
left a comment
There was a problem hiding this comment.
The only breaking change is a dropping of support for node 8.
Lgtm.
|
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
This pull request has been automatically closed because it has not had activity in the last 37 days. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
Ping for merge |
|
@holopin-bot @RafaelJCamara Thank you! Here's a digital badge as a small token of appreciation. |
|
Congratulations @RafaelJCamara, the maintainer of this repository has issued you a badge! Here it is: https://holopin.io/claim/cmbs0ywk61076507laa8hyd04r This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
Description
When doing a
npm installwe get flagged that there are packages with vulnerabilities.Before:

After:

Issue reference
No issues were mentioned.
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: