This repository has been archived by the owner on Feb 3, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 202
NPM reports hundreds of vulnerabilities #108
Labels
Comments
I'm aware. Now that Node 10 LTS is out I need to run updates and get it running on that release (a few users mentioned trouble with Node 10). I'm extremely busy with the upcoming Surreal CMS release right now so if anyone wants to work on this let me know! |
I am already working on it till date i update the sequlize classes, alot of
updates are in queue, i will generate a PR soon for postleaf.
…On Wed, Mar 6, 2019, 9:26 PM Cory LaViska ***@***.***> wrote:
I'm aware. Now that Node 10 LTS is out I need to run updates and get it
running on that release (a few users mentioned trouble with Node 10).
I'm extremely busy with the upcoming Surreal CMS
<https://www.surrealcms.com/> release right now so if anyone wants to
work on this let me know!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#108 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC0DcDS-qWzfmDwp5GvJWpBf3lq9CrYHks5vT-U3gaJpZM4bgV_2>
.
|
Beautiful! Are you using Node 10 LTS? |
Yes.
…On Wed, Mar 6, 2019, 9:45 PM Cory LaViska ***@***.***> wrote:
Beautiful! Are you using Node 10 LTS?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#108 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC0DcDIK7DAAAwcBx0RnLCQvH5VCKFHsks5vT-mOgaJpZM4bgV_2>
.
|
@post2seth did you get this working? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary
NPM reports vulnerabilities regarding the packages installed:
"found 470 vulnerabilities (245 low, 203 moderate, 21 high, 1 critical)"
Steps to Reproduce
Additional info
Note: This issue tracker is ONLY for bug reports and feature requests. If this is a personal support issue, please visit postleaf.org/support.
The text was updated successfully, but these errors were encountered: