I have these gulp tasks to preprocess my css and html. months ago it was all polished and working great.

I run the commands today, npm complains about deprecated something and doesn't let me run... I do updates, I try to run again: "Right now osX is not supported".

I literally did not change anything all these months.

Fuck you npm.

Guess someone is too stupid to check the new versions dependencies. Besides, you’re using gulp, presumably with a shitty plug-in that does something completely dum and useless, so I’m not even mad. Who tf uses gulp in 2022….

any chance you updated your Mac to Monteray or other version in that time?

I had mac updates fuck my system before, specifically it removed Git and GPG once for me.

On the other hand though, these "modern" package managers are starting to get really annoying. I have the same issues with pythons pip weirdly enough. Sometimes you just don't mess with a project but updates to the package manager or to your environment can completely thrash your setup. in my case I usually just purge everything and then re-install my virtual environment from scratch and that does the job. For you the equivalent should be deleting node_modules and re-installing all of those with npm -i or whatever.

But why is this still happening today is beyond my understanding. One would expect that standards, abstractions and specifications would prevent things from breaking in these ways ^^;

i mean... the moment package managers decided that your app's dependency isn't on the lib code locally downloaded at the time of project creation, but instead permanently on the current most recent remote version of the lib... is the moment right after the one when creators of those package managers should have been shot.