npm / npm / 8437

93%

master: %

push

travis-ci

<a href="https://github.com/npm/npm/commit/<a class=hub.com/npm/npm/commit/8e979bf80fb93233f19db003f08443e26cfc5e64">8e979bf80<a href="https://github.com/npm/npm/commit/8e979bf80fb93233f19db003f08443e26cfc5e64">&quot;&gt;Revert &amp;quot;install/deps: Stop flattening modules that require peer deps&quot;

This reverts commit </a><a class="double-link" href="https://github.com/npm/npm/commit/<a class="double-link" href="https://github.com/npm/npm/commit/06c154fd653d18725d2e760ba825d43cdd807420">06c154fd6</a>">06c154fd6</a><a href="https://github.com/npm/npm/commit/8e979bf80fb93233f19db003f08443e26cfc5e64">.

This caused problems because folks were using peer deps to indicate that the
target of the peer dep needed to be able to require the dependency and had
been relying on the fact that peer deps didn&#39;t change the shape of the tree
(as of npm@3).

The fix that will actually work for people is for a peer dep to insist on
never being installed deeper than the the thing it relies on.  At the moment
this is tricky because the thing the peer dep relies on may not yet have
been added to the tree, so we don't know where it is.

3640 of 5191 branches covered (70.12%)

6779 of 8007 relevant lines covered (84.66%)

1546.19 hits per line