Show HN: ied – an alternative package manager for Node

Hey everyone!<p>I made this. I&#x27;m happy to answer any questions, but please bear in mind that this is a WIP. There is still a lot of work to be done, although feature parity with npm is <i>not</i> the goal.<p>Upcoming features are:<p>* Nix-like rollbacks * built in registry server * discovery + installation via BitTorrent DHT<p>Would love to get any feedback!

That seems so cool. One question is how compatible is with npm? Can I use it as a drop-in replacement ( talking about the CLI tool )?

Cloned a popular project (babel) and on a MacBook Pro:<p><pre><code> npm install 52.28s user 8.08s system 73% cpu 1:22.41 total ied install 10.22s user 4.36s system 142% cpu 10.230 total </code></pre> Impressive.

You say you are creating a more performant NPM. Is it impossible to fix the current NPM? Why not submit fixes back to NPM? Why create a new project?

I never thought to myself, &quot;wow, npm is slow.&quot; Is that really the core problem this is solving?

<i>&gt; The easiest way to install ied is using npm</i><p>Bootstrapping ftw.

&gt; produces a flat node_modules directory<p>Finally. npm&#x27;s node_modules makes Node on Windows unbearable from time to time.<p>Shut up and take my money!

Unfortunate naming ie <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Improvised_explosive_device" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Improvised_explosive_device</a>

Guys NPM is not the problem, Javascript is.