Zoltan Kochan 5d04767778 fix: peers are resolved similarly during named and general install (#726) ...

* fix: peers are resolved similarly during named and general install

There is no need to always run a general installation for
creating a predictable `node_modules` structure. If peers are
resolved from top dependencies, the peers are not linked to
the dependent package. The dependent package can see such peers
w/o additional manipulations

Ref #724

* fix: don't print warning when peer is resolved from top dep

* test: verify the peer warning are reported correctly

2017-04-26 14:40:45 +03:00

..

auth.ts

test: installing of private package from shrinkwrap

2017-04-25 22:28:47 +03:00

fromRepo.ts

fix: installation of packages from non-github repos

2017-04-23 20:09:37 +03:00

fromTarball.ts

fix: the correct spec is saved in package.json

2017-04-14 09:38:43 +03:00

index.ts

test: add auth tests

2017-04-25 19:50:43 +03:00

installationChecks.ts

test: divide installation tests to separate files

2017-04-02 21:46:37 +03:00

lifecycleScripts.ts

feat: use npm's config system

2017-04-20 23:01:14 +03:00

misc.ts

fix: global installation always works now (#713)

2017-04-22 23:11:25 +03:00

optionalDependencies.ts

test: divide installation tests to separate files

2017-04-02 21:46:37 +03:00

peerDependencies.ts

fix: peers are resolved similarly during named and general install (#726)

2017-04-26 14:40:45 +03:00