NPM v4.0.0

After using yarn for a week, I can&#x27;t imagine going back to npm.<p>I use npm 90% for install, and yarn does this so much better.<p>Installs are 3-4 times faster. Output is minimal and readable (compared to npm&#x27;s wall of text that I never read). Packages are cached so I can work with slow connections in coffee shops.<p>Sorry to be blunt, but I feel none of the release features gonna help my daily usage of npm. How about actually fixing the tab completion, which has been slow and broken forever?

&gt; Keep an eye out for npm@5 in Q1 2017. We&#x27;re planning a major overhaul of shrinkwrap as well as various speed and usability fixes for that release.<p>So the most interesting part of npm4 release are the announced improvements that are coming in npm5 :)

Are the NPM guys working on a parallel download feature to speed things up? Have they even noted it as a feature to be implemented? Speed and pkg locking are the only two features that make me use yarn. If they were in npm then most people wont worry about yarn at all I guess.

&gt; npm&#x27;s default git branch is no longer `master`. We&#x27;ll be using `latest` from now on.<p>Is there any reason to do this?

NPM is so Oct 10 2016.

I&#x27;m glad for the relatively low amount of breaking changes this time. npm prepare should be a nice addition (using prepublish for, e.g., installing typings is such a non obvious hack).<p>That said, I&#x27;m still not certain about shrinkwrap excluding dev deps. I mainly use it to ensure my build agent uses the same dependencies as my dev box, and at a time when things like babel pull in a ridiculous amount of sub dependencies, it really does not make sense to not lock down _all_ your dependencies by default.

npm search will at least return results now ahah. I didn&#x27;t know about <a href="https:&#x2F;&#x2F;npm.im&#x2F;npms-cli" rel="nofollow">https:&#x2F;&#x2F;npm.im&#x2F;npms-cli</a> , sounds like a great alternative. Thanks for sharing this release here :)

&gt; npm scripts no longer prepend the path of the node executable used to run npm before running scripts. A --scripts-prepend-node-path option has been added to configure this behavior.<p>Why? That seems like a good default, something most people would need.