4 ms·
> TC39 is currently working on over 30 active proposals. What else does the future hold in store? These days we download our packages from npm. I am surprised
by flavio81 9y ago
> TC39 is currently working on over 30 active proposals. What else does the future hold in store? These days we download our packages from npm.
I am surprised that no more mentions of NPM were made. I hope that commitee TC39 addresses the topic of NPM and tries to create a new version that is standarized and that elliminates the serious flaws of NPM, which for me are one of the major hindrances to adopting Node.js for things that go beyond prototyping.
- idbehold 9y agoTC39 has no affiliation with Node or its package manager. It's only for the ECMAScript language specification.
- k__ 9y agoWell, the module spec tries to be a standard for Node AND browser modules
- dean177 9y agoNo mentions of npm are made because this is about language specification not the broader ecosystem around javascript. Package managers are completely detached from language specifications so that they can evolve independently.
- k__ 9y agoWell, npm got faster over the years and with v5 they got consistent hashing for versions, which should make deployment much safer.
- seangrogg 9y agoOut of curiosity, have you seen the latest changes to npm? Since they've added lockfiles I've yet to have any issues with dependency management, really.
- flavio81 9y agoThanks for your reply, Sean. Googling on lockfiles i found out more about the features of the Yarn package manager. Perhaps that's what I should use. However what i meant with my comment is that I feel that package managers should be standarized into a language -- as long as the package registry is not private but can be pointed to whatever URL one wants.
- root_axis 9y agoyarn is a great alternative to npm