It is an uphill battle, lemme tell you. There is a bit of a culture clash inside Javascript. Even when you're a veteran contributor, sometimes maintainers resi

It is an uphill battle, lemme tell you. There is a bit of a culture clash inside Javascript. Even when you're a veteran contributor, sometimes maintainers resist changing packages, as simple as they are, because there is an implicit assumption that popular packages, or even packages with too many dependencies are "better" or "handled all the edge cases". Even with careful evaluation of the options and a write-down of issues and a proper comparison, you need ten times as much energy to remove a package than it took to add it. It's even worse is when "too many packages" is in the DNA of the package you're collaborating.