NPM and the whole dependency tree for JS packages should burn in the pits of hell.
Let's pretend that uninstalling a single (albeit larger) module didn't take 8 minutes and that it didn't spit out 20 warnings from a total of 277 (HOLY FUCK) related packages.

How can you guys (JS-only devs) handle this ?!

Programming in JS seems to inflict such unbearable pain that nothing matters anymore.

(Not a JS dev)

@IntrusionCM I'm gonna write a package for checking if anything matters anymore. It'll consist of a single exported nullary idempotent function that returns "false". As a string because JS.

By using overly large dependencies when they are needed. Never really had damn near all of the issues people mention about node packages and issues of the like for project. In the weird case in which i have fucky stuff happening i jusr delete the node modules folder and reinstall what i need.

🤷‍♂️ i have 2 very large node apps running in production that have never given me any issues man, like at all. Maintaining them is cake also.

I'll go out on a limb and say JS-only devs aint devs 🤷

@AleCx04 You're apparently one of the lucky ones if you've never run into a retarded issue at least once. I also have multiple services written in Node in prod, and I always head headaches when it comes to deps. Sometimes larger, sometimes lesser.

@AleCx04 I'm just saying that package mngrs for other languages simply work better. I know that JS ecosys is huge but that's not an excuse for a package having 500 dependencies. People should look up to lodash and packages alike. God bless them.

try yarn to see if it cures your whining

And this is why I prefer Python. PyPI is a mess but it's still better than npm.

What package is it though?

@M1sf3t MBP

@jesustricks I did use Yarn. It caused my whining.

@mvelebit what exactly are you installing? that rarely happens unless it's compiling something or downloads some bug binary

@IntrusionCM not for me, sorry

git gud I guess

@jesustricks I was uninstalling @babel/cli to be exact.

if you don't mind, you can send me the package.json with yarn.lock before removing @babel/cli so I can try it here with a hdd