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

..

install

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

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

packages

fix(link): don't reinstall linked packages

2017-02-17 20:33:43 +02:00

utils

fix: global installation always works now (#713)

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

api.ts

feat: use a shrinkwrap file instead of graph.yaml

2017-03-13 21:23:41 +02:00

breakingChanges.ts

feat: recreate node_modules only with general installation

2017-04-05 23:06:18 +03:00

cache.ts

feat(shrinkwrap): respect shrinkwrap.yaml for top deps

2017-03-04 21:57:39 +02:00

cli.ts

fix: rewrite packages added by other package managers

2017-04-24 17:47:30 +03:00

index.ts

feat: rename pnpm verify to pnpm store status

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

link.ts

fix: global installation always works now (#713)

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

offline.ts

feat: add offline support

2017-03-13 02:31:37 +02:00

prune.ts

feat: use a shrinkwrap file instead of graph.yaml

2017-03-13 21:23:41 +02:00

shrinkwrap.ts

fix: the correct spec is saved in package.json

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

storeStatus.ts

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

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

uninstall.ts

test: fix uninstallation tests

2017-04-17 11:18:24 +03:00