So you're having issues with a few components of the ecosystem, why are you taking it out on the language itself?
npm modules are not an integral part of the language. It's just an optional add-on that you might explore on your own to get work done for you more easily and more efficiently.
If you're lucky and found a module that fits the bill perfectly for a given project, that's awesome. If not, that's fine too. You can either fork the module and extend it as you like or build a new one from scratch.
I don't know why you would expect to find npm modules that can get the job done 100% for you and all the time?
That's a totally unrealistic expectation and unreasonable.
If everything that we devs need is ready-made and our jobs relegates to only gluing stuff together like entry-level technicians, don't you think that would be detrimental to our profession as a whole as it would be a few clicks away for a bot or an algorithm to automate our jobs away?