Replies: 2 comments
-
Nope, you shouldn't worry |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you for the link. It was educational. That poor guy must be out of
his mind with frustration if almost three years after his article, we are
in the same place.
…On Fri, Feb 16, 2024 at 6:42 AM Julien Ripouteau ***@***.***> wrote:
Nope, you shouldn't worry
https://overreacted.io/npm-audit-broken-by-design/
—
Reply to this email directly, view it on GitHub
<#4410 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJXG7XSWSOSUKPIECU5XF3YT5V7HAVCNFSM6AAAAABDMEVONGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DIOJTGU2TM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Frederick R. Polli
***@***.***
Additional contact information available upon request
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I init Adonis with the API starter kit and when I try to install another package (vite or bouncer are what I have tried), I get this from npm:
Ok, so I run npm audit to see what they are:
This looks bad. If I take npm's advice and fix these vulnerabilities, I am unable to install a functioning server. If I ignore them and just forge ahead, I get to the beloved "started HTTP server on localhost:3333" message.
When I do select fix, I get a whole lot of peer dependency warnings or even errors.
So, do I need to worry about these high severity vulnerabilities? It sounds bad. Hackers are like water.
Thank you for your time.
Beta Was this translation helpful? Give feedback.
All reactions