CAN'T FIX FOUNDED VULNERABILITIES !!!!

[fkazadi2]

• [email protected]
  added 20 packages from 3 contributors, removed 68 packages, updated 23 packages and audited 340 packages in 220.833s

1 package is looking for funding
run npm fund for details

found 4 vulnerabilities (3 low, 1 high)
run npm audit fix to fix them, or npm audit for details

[lowwk1234]

1. get the same problem. Try npm audit fix - the issue remains. Pls advise if this will cause problem down the road. Thx

[saj120]

I am experiencing the same problem. Pls let me know when rectified.

[00cm]

1. get the same problem. Try npm audit fix - the issue remains. Pls advise if this will cause problem down the road. Thx

I think this will be okay for learning purposes. Just don't go live with anything that you create here. For me, I ran npm audit fix and it fixed all 100+ vulnerabilities except one. But now I know which package I am going to avoid when I build my own websites. :)

[Tonydarkness]

I don't know if anyone still experiences this, but the async package is outdated and has high severity vulnerability, so it's better to uninstall the vulnerable packages by using npm uninstall <package-name> including async, browser-sync, port-scanner, and lite-server. Then, use npm install async to install the latest version. If you wanna preview the HTML files, use the live preview extension from Visual Studio Code instead.