That's only a problem in the JavaScript world - the Java, Kotlin, Dart and many other languages have well defined ways of doing certain things and any new things are often designed first with a consortium of engineers and then built once which means things are generally released in such a way, that staying up to date is fairly doable and the solutions are generally complete.
Whereas in the JavaScript world everybody builds their own solution for problems that are often not even well defined, everybody wants to be THE expert spewing article after article on how things should be done, everybody wants to build the next big framework that often just overlaps existing solutions and and there's generally a gazillion different ways of doing the same things.
How many build tools are there in Java? Maven and Gradle are almost the defacto standards and they do everything (gradle uses maven packages). Same in Dart, one build tool, Pub, which does everything. How many tools do you need to do everything in JavaScript?
Grunt or Gulp or Broccoli or Brunch or Feri or Mimosa or Angus or Lineman or let's throw in some Babel, Webpack, Browserify, you've got NPN as package manager instead of NPN doing what all the other tools are doing ... then there's Bower trying to do what NPN is doing, Jam, Ender, volo, Component, JSPM, ... this is madness !
PS, try this Tool.JS thing I'm building, it solves all the above problems I've mentioned with the above tools.