title: What is the difference between unmet and incorrect peer dependency?
body: <p>I believe I understand what "unmet peer dependency" means. For example "package-a" depends on "package-b@^2.1.5" but no version of package-b@2.x.x (>=2.1.5) is installed.</p>
  
  <p>But "incorrect dependency" baffles me. It would make no sense to say "package-a is asking for an incorrect dependency". Is it saying that the dependency listed in package-lock.json or yarn.lock doesn't match what package-a says it needs? If this is correct, then how would this be resolved?</p>
  
  <p>When I search for specific discussion about "incorrect dependency" on Github, it seems to show up on issues in the yarn or npm repos. And the resolution usually seems to be a fix to yarn or npm. Is this message for bugs in yarn/npm?</p>
  
  <p>If I search <a href="https://docs.npmjs.com/" rel="noreferrer">https://docs.npmjs.com/</a> for "incorrect peer dependency", I get no results.</p>