3 ms·

NPM – Next Generation Package Management

• chatmasta 8y ago
  npm is trash, with horrible performance and a horrendous security track record. At this point there is zero reason to use npm over yarn. Now this? Why would I ever trust a brand new (and thus full of undiscovered bugs) product from the same company behind npm?
  • swingline-747 8y ago
    yarn is really fast, and I detest any integrations that force npm. Why don't they just standardize on yarn? Oh sorry, I forgot about mandatory js fragmentation and NIH syndrome. Mea culpa. ;)
• voidr 8y ago
  I prefer to have a package manager, that I control, rather than having a runtime that can randomly go out to the internet and download code, while I'm trying to run the application itself.
• officialchicken 8y ago
  In js world, the ideal solution for lack of security, poor uptime, no file/package integrity, bloated packages, and fragmentation hell... is to replace node.js runtime with something that can do background downloads and place the files in a global location? And it should include a template engine, a bundler, transplier, kitchen sink, etc. Does NPM have any engineering leadership?