<story><title>Disabling npm&apos;s progress bar yields a 2x npm install speed improvement</title><url>https://twitter.com/gavinjoyce/status/691773956144119808</url></story><parent_chain><item><author>mbell</author><text>I agree, but I&amp;#x27;m curious what other build systems have a lock file?&lt;p&gt;Ruby does through bundler, who else does this right? I can&amp;#x27;t think of any.</text></item><item><author>juandazapata</author><text>That&amp;#x27;s frustrating, I got bitten by that a couple of times. I&amp;#x27;m wondering when will they add a LOCKFILE like every other build system out there :&amp;#x27;(</text></item><item><author>yunong</author><text>Even more important, npm doesn&amp;#x27;t reliably reproduce builds. Different runs of the same shrinkwrapped build could either fail or succeed -- which is odd given that builds should be deterministic. Additionally, shrinkwrap is also broken in the same way.&lt;p&gt;This is the first time I&amp;#x27;ve heard of ied, a little competition could go a long way!</text></item><item><author>untog</author><text>Progress bar or not, npm has gotten extremely slow with v3, to the extent that someone is working on a performance-centered alternative called ied:&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;gugel.io&amp;#x2F;ied&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;gugel.io&amp;#x2F;ied&amp;#x2F;&lt;/a&gt;&lt;p&gt;installs are literally the #1 thing npm needs to do well, and I really hope we see some improvement soon.</text></item></parent_chain><comment><author>stormbeta</author><text>You get a similar effect for free with any language whose community defaults to non-floating transitive dependencies, e.g most JVM languages.</text></comment>
<story><title>Disabling npm&apos;s progress bar yields a 2x npm install speed improvement</title><url>https://twitter.com/gavinjoyce/status/691773956144119808</url></story><parent_chain><item><author>mbell</author><text>I agree, but I&amp;#x27;m curious what other build systems have a lock file?&lt;p&gt;Ruby does through bundler, who else does this right? I can&amp;#x27;t think of any.</text></item><item><author>juandazapata</author><text>That&amp;#x27;s frustrating, I got bitten by that a couple of times. I&amp;#x27;m wondering when will they add a LOCKFILE like every other build system out there :&amp;#x27;(</text></item><item><author>yunong</author><text>Even more important, npm doesn&amp;#x27;t reliably reproduce builds. Different runs of the same shrinkwrapped build could either fail or succeed -- which is odd given that builds should be deterministic. Additionally, shrinkwrap is also broken in the same way.&lt;p&gt;This is the first time I&amp;#x27;ve heard of ied, a little competition could go a long way!</text></item><item><author>untog</author><text>Progress bar or not, npm has gotten extremely slow with v3, to the extent that someone is working on a performance-centered alternative called ied:&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;gugel.io&amp;#x2F;ied&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;gugel.io&amp;#x2F;ied&amp;#x2F;&lt;/a&gt;&lt;p&gt;installs are literally the #1 thing npm needs to do well, and I really hope we see some improvement soon.</text></item></parent_chain><comment><author>sync</author><text>Mix, Erlang&amp;#x27;s package manager (used by Phoenix &amp;#x2F; Elixir)&lt;p&gt;Cargo, Rust&amp;#x27;s package manager&lt;p&gt;Meteor</text></comment>