Why can't NPM has something like Apache commons? There you can include all simple and fundamental functionality. Instead of having one package each like this.
Much of the terribleness of the current programming environment could have been rectified if this fundamental failure had not been allowed to continue.
https://www.davidhaney.io/npm-left-pad-have-we-forgotten-how...
Stupid debates over a formatting tool - or in this case, a simple conditional - should tell you that something is seriously FUBAR in Javascriptland.
But yes, a JS stdlib would solve 95% of the joke-level problems with the ecosystem.
In fairness, I should mention that I haven't written much javascript myself over the years, so using CRA to quickly get a simple SPA off the ground has been rather nice of late.
It's opinionated and has worts, but ~3 commands and you're 'off the the races' is hard to argue against.
The "current programming environment" is the problem, and it doesn't exist because Javascript is superior to other languages, and should be used everywhere, but only because web developers are easier to find and cheaper to hire.
And in any case, you could ship a "standard library" for javascript that covers most common use cases in a single static file. We used to do that, it was called JQuery. Even assuming for the sake of argument that Javascript's standard library is lacking, that doesn't justify the mess that is Node's micropackages.
Because it's consensus-driven, and that consensus is achieved on meetings organized every ~3 months.
And because of strict backwards compatibility rule, everyone is extremely cautious.
I tried to add new methods to Set, but proposal is basically being held hostage by subclassing proposal. https://github.com/tc39/proposal-set-methods