Yarn: Print more details on "Unmet peer dependency" warning

Created on 30 Oct 2016 · 6Comments · Source: yarnpkg/yarn

Do you want to request a _feature_ or report a _bug_?

Feature.

What is the current behavior?

When I add multiple packages and one/some of them cause Unmet peer dependency warning, there's no way to figure out which package(s) cause this except manually go through their package.jsons.

What is the expected behavior?

Print which package(s) cause warning.

Please mention your node.js, yarn and operating system version.

macOS v10.11.6
node v7.0.0
yarn v0.16.1

Source

alexfedoseev

👍35

Most helpful comment

yarn check lists some info. (I'm in yarn 0.18.1)

rockymeza on 28 Dec 2016

👍4

All 6 comments

How do you get info on missing peer dependencies after the initial warning on install? Is there some command that lists this info (like npm ls does after listing the installed packages)?

dlong500 on 24 Dec 2016

👍2

yarn check lists some info. (I'm in yarn 0.18.1)

rockymeza on 28 Dec 2016

👍4

@bestander I'm not sure this is resolved/fixed in 0.18.1. After install, I still only see:

warning Incorrect peer dependency "meanie-express-error-handling@^1.0.3".

It doesn't specify which package is asking for the peer dep, which is vital information.

Only after doing yarn check does it show up as an error:

error meanie-express-jwt-service#meanie-express-error-handling@^1.0.3 doesn't satisfy found match of [email protected]

Is this expected behaviour? Can we use the same message for the warning during installation so that we don't have to issue two commands to get the info we need?