Fuck third-party's third-party dependencies which break your third-party dependencies

@horus hmmm I believe it would..!

Welcome to NPM hell.

It’s a special place where you should always use someone else’s code because it’s somehow better and more reliable, and if it isn’t then it isn’t your fault or responsibility! See also: code communism.

It happens with other platforms too. Flutter's cached_network_image hasn't been updated for 7 months, dependency stucks at http version 0.37 while other third party libraries needs http version 1.1 already.

I ended up rolling my own cached network image widget. I feel much better now.

Moral of the story, stop depending on too much third party libraries, which may not be updated by their creators. Especially when the creators make no profit off them.

@Root beat me to it, I was going to ask the OP if they was playing with node lmao

@AleCx04 😁

@AleCx04 @Root even though I have experienced it with npm as well, this particular rant was about Python!
To be honest, it's the first time that I've had this with Python dependencies but it doesn't make it any better.. Got a solution nonetheless but took way too much time.

@daniel-wu yeah I luckily learned this lesson hard and early in my career, but very good advice for anyone!

@Bibbit oh man those can be a bitch also