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

..

dirsum.ts

fix: use @zkochan/dirsum instead of dirsum

2017-02-06 20:41:01 +02:00

expandTilde.ts

fix: resolve local-registry config

2017-02-27 00:10:01 +02:00

getPkgDirs.ts

perf: filter package dirs asynchronously

2017-02-25 16:17:29 +02:00

gracefulify.ts

fix: too many open files

2017-02-27 00:09:24 +02:00

modulesController.ts

fix: store status doesn't fail on skipped optional deps

2017-04-09 14:06:49 +03:00

readPkg.ts

fix(package): package.json should not be normalized

2017-02-12 02:41:06 +02:00

safeReadPkg.ts

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

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

shrinkwrap.ts

feat: rename pnpm verify to pnpm store status

2017-03-23 21:36:28 +02:00

storeController.ts

refactor(fs): use packages for loading/writing YAML files

2017-02-12 13:25:04 +02:00