What is the current behavior?
- Install dependency A (with transitive dependency AB)
- Later (contrary to #2132), install dependency C (which has AB as peer dep) — an unmet peer dependency warning appears, even though AB was installed in the first step.
Step 1 output (notice that
storyboard-core is installed as a normal dependency of
$ yarn init -y $ yarn add firstname.lastname@example.org yarn add v0.19.1 info No lockfile found. [1/4] Resolving packages... [2/4] Fetching packages... [3/4] Linking dependencies... [4/4] Building fresh packages... success Saved lockfile. success Saved 13 new dependencies. ... ├─ email@example.com ├─ firstname.lastname@example.org ... Done in 4.25s.
Step 2 output (with
storyboard-core in its
peerDependencies; notice the warning):
$ yarn add email@example.com yarn add v0.19.1 [1/4] Resolving packages... [2/4] Fetching packages... [3/4] Linking dependencies... warning "firstname.lastname@example.org" has unmet peer dependency "storyboard-core@^3.0.0-rc.0". [4/4] Building fresh packages... success Saved lockfile. success Saved 1 new dependency. └─ email@example.com Done in 1.36s.
Despite the warning, the installation is successful. Also note that no peer-dep warning appears with
What is the expected behavior? No warning, since the peer dependency is already installed (with exactly the required version).
Please mention your node.js, yarn and operating system version.
Windows 7 (also observed in OS X Sierra)