5 ms·
Isn't the first party solution NPM?
by imbnwa 5y ago
Isn't the first party solution NPM?
- inopinatus 5y agoThe first-party solution is ES Modules. Node is not Javascript.
- codetrotter 5y agoES Modules aren't package management though? In that ES Modules say nothing about how to get the modules in the first place, nor anything about versions. Not in any standardized way anyhow.
- inopinatus 5y agoSolutions are defined by the problems they address, not the mechanics of how they address them, or even particularly how good or thorough they are. Which is to say, yes, it’s painfully half-baked and riddled with inconsistencies. But that is pretty typical of JavaScript anyhow.
- codetrotter 5y ago> Solutions are defined by the problems they address, not the mechanics of how they address them, or even particularly how good or thorough they are. 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.
- inopinatus 5y agoNo, that’s still fixating on the mechanics, not the problem. Package management is not a valuable outcome, it’s a means to an end. 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.
- mbesto 5y agoYou mean the npm, which is maintained by npm Inc., a subsidiary of GitHub (Microsoft)? IMO, that's where the problem lies.
- kall 5y agoIt still ships with node, right? So yeah.