Zoltan Kochan b396b02db4 fix: peers resolution in a monorepo ...

This issue was happening when two workspace packages had the same
dependency and that dependency depended on a peer dependency.
This dependency was resolved with the same peer dependency
in every workspace package even if the peer was different in
different workspace packages.

PR #1988

2019-09-01 20:47:52 +03:00

..

getAllDependenciesFromPackage.ts

refactor: create @pnpm/resolve-dependencies

2018-10-01 10:04:23 +03:00

getSaveType.ts

refactor: use DEPENDENCIES_FIELDS from @pnpm/types

2018-09-21 21:34:23 +03:00

getWantedDependencies.ts

fix: dependencies should always be explicitly grouped with peers

2019-05-28 22:41:07 +03:00

index.ts

fix: "pnpm store add" should read the registries of scoped pkgs

2019-03-25 00:58:56 +02:00

nodeIdUtils.ts

fix: peers resolution in a monorepo

2019-09-01 20:47:52 +03:00

normalizeRegistries.ts

feat(shrinkwrap): don't save registry URL in shrinkwrap v4

2018-10-20 20:12:28 +03:00

pickRegistryForPackage.ts

fix: "pnpm store add" should read the registries of scoped pkgs

2019-03-25 00:58:56 +02:00

realNodeModulesDir.ts

feat: create @pnpm/utils

2018-05-13 00:55:25 +03:00

safeReadPkg.ts

style: use standard style with trailing comma

2018-10-07 16:39:49 +03:00