-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Unmet peer dependency" with peer dependency already installed as transitive dep #2688
Comments
Still seeing in
|
…4478) **Summary** Fixes #4446, fixes #4433, fixes #2688, fixes #2387. Follow up to #3803. The fix in #3893 was too aggressive, allowing only top-level dependencies to be used in peer dependency resolution which was incorrect. This patch allows resolving peer dependencies from the same or higher levels in the dependency tree. **Test plan** Additional unit and integration tests.
@BYK I updated yarn based and the still persists for me when installing
Any help would be appreciated. |
@javonclarke this issue is not fixed in 1.0.2, only on nightlies right now: https://yarnpkg.com/en/docs/nightly |
@BYK Ah thank you. |
@BYK Thanks for the effort! |
…arnpkg#4478) **Summary** Fixes yarnpkg#4446, fixes yarnpkg#4433, fixes yarnpkg#2688, fixes yarnpkg#2387. Follow up to yarnpkg#3803. The fix in yarnpkg#3893 was too aggressive, allowing only top-level dependencies to be used in peer dependency resolution which was incorrect. This patch allows resolving peer dependencies from the same or higher levels in the dependency tree. **Test plan** Additional unit and integration tests.
I can reproduce the issue using OP's instructions in
I checked on http://jubianchi.github.io/semver-check/, and it says that " |
Is there anything I can do to help with a repro case? The Storybook issue is pretty much exactly what I'm seeing in my project as well on the latest release. |
@Hypnosphi @greggb I think this is a separate issue. Sounds a bit like #4850 so feel free to comment there and follow it. |
@BYK Do yo mean the one in storybook? Yeah, probably. But note that this one is also reproduceable right now |
@Hypnosphi commenting under a closed issue won't get us any visibility, that's why I'm promoting an already open issue which seems like what you are reporting here :) |
Should I open a new one instead, with exactly the same title and body? I just followed instructions from #2688 (comment) and got the same warning as OP using |
@Hypnosphi yes, with a repro repo so we can reproduce locally without any other context of information and then fix it. |
Thanks BYK |
Bug
What is the current behavior?
Repro
Step 1 output (notice that
storyboard-core
is installed as a normal dependency ofstoryboard
):$ yarn init -y $ yarn add storyboard@3.0.0-rc.1 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. ... ├─ storyboard-core@3.0.0-rc.0 ├─ storyboard@3.0.0-rc.1 ... Done in 4.25s.
Step 2 output (with
storyboard-core
in itspeerDependencies
; notice the warning):Despite the warning, the installation is successful. Also note that no peer-dep warning appears with
npm install
.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.
Node v7.3.0
yarn v0.19.1
Windows 7 (also observed in OS X Sierra)
The text was updated successfully, but these errors were encountered: