Bundler, AFAIK, isn't first-party, its a separate team and project.
Historically, IIRC, gems wasn't even first-party
Good standard solutions are often the outcome of multiple competing efforts pushing forward, proving what works, and proving what doesn't.
But, it's irrelevant. I'm not arguing no one should make a third-party package manager, just that there should be a standard, ideally first-party one, that is good and well supported.
Languages like Ruby, Rust, Swift have recognized it is beneficial for the core project to provide a package management solution.
Which is to say, yes, it’s painfully half-baked and riddled with inconsistencies. But that is pretty typical of JavaScript anyhow.
Yeah but what I mean is that as it stands you literally cannot implement a package manager based on ES Modules alone. So it’s strange to me that someone would say that ES Modules are the package management solution for JavaScript. That’s not what it is currently for. Though the relevant standards may certainly be officially extended in the future, to allow for standardized package management based on ES Modules.
In principle, ES modules do away with needing a package manager. And yes, folks are already working on the consequential gaps in capability.
The point still being, however incomplete it currently is, this is the first-party solution. Node is not JavaScript.