Just another day fun as hell day with old JavaScript

It literally tells you how to fix it.

To be fair, you could write javascript with no npm modules, so it's not really javascript's fault

@nibor That's like saying you can walk, so why complain about a broken car

@10dev it's often like someone not going to the shop at the end of their road because their car has a broken unnecessary gadget, when they could walk there in 5 minutes

@10Dev lol how do you even achieve this?
Did you explicitly use the least popular packages?

@nibor Except it's not a 5 minute walk, though. It's usually a 10 mile run and a swim across the amazon river.

No, it's not Javascript's fault but I doubt you'd also have enough time to rewrite all 92 plugins.

Which is why I abhor working with JS.

Looks like a typical old JS project with too many dependencies that is being spun up again after 2 years of being dormant. This doesn't happen on a day to day basis in an ongoing project.

Its good there is a tool that lets you know about it, but stop with the dependency hell already.

@theuser @nitwhiz yeah, this is js that I'm bringing back from the dead. Normally it isn't this bad

@10Dev Not really sure what you should do, I highly doubt you have the time to sort it out. Sounds like weeks upon weeks of updating and testing.

@theuser yeah I'm probably just gonna start again. This isn't worth updating almost 100 packages

JavaScript is literally the only language that tells you your vulnerabilities when you install a new module.

As much as I know, other programming languages OBVIOUSLY have vulnerabilities too, but nobody tells you

JS devs be like:
- pulling in 10 GB of trash from all over the internet
- waking up to dependency hell
- blaming JS

@Fast-Nop heeyyy after spending 60 hours slapping my dick around webpack 5, I got it down to 4 megs!! gzipped and minified

How much of that gazillion packages are you actually using?

exactly, those are only the errors? how many packages do you actually need??

@nibor this is the way.

npm audit fix --force
npm t #does any test fails? If not then keep going
npx npm-check -y #or -u if you want to be selective
npm t

And you should be good to go. Of course, if it's really outdated and reliant on deprecated packages, then it would be risky, but that's good enough to fix most of the dependencies without manually upgrading them.