Miss Dada  🏳️‍⚧️

I'm on day two of a completely normal "update all of our dependencies" cycle and it feels like it will never end. Really making me wish I weren't married to the Node+npm ecosystem. No other ecosystem that I've worked in has been like this.

Apparently those popularity rankings that I quoted were wrong, because sorting by "popularity" in NPM doesn't seem to sort by popularity.

Does anyone except me care about any of this? It feels like everyone else is content to have everything break at random on a daily basis, then often stay broken for months or sometimes forever. (This is an actual question; I don't mean it dismissively.)

I don't know how NPM rates "popularity", but as one of the maintainers of a package registry I can guarantee it is almost certainly worse than what you'd get if you Google "node + think you are trying to do" (and that may have the same result in which case ¯\_(ツ)_/¯)

Gave that a try and got the abandoned-for-7-years package followed by some other packages that have fewer weekly downloads than the one that's broken.

That may just be what folks are using though. Abandoned for 7 years means it's for sure something other than commonmark, but maybe that's fine?

it has 2% as many weeklies as the other one though

2% almost certainly means the one with more downloads is in fact is more used, but download count is an inherently flawed metric. Package a which is depended on by package b is always going to have >= download count of b, and a may not be the package app code is picking