未满足的peer dependency与错误的peer dependency的区别是什么？

Hey there! Let's start by confirming your understanding first—you're totally right about unmet peer dependency! That's exactly the scenario where a package (like package-a) requires a specific version range of another package (e.g., package-b@^2.1.5), but no version of package-b that meets that range is installed in your project.

Now, let's clear up the confusion around incorrect peer dependency (since that's the term you're seeing in tool warnings):

What is an Incorrect Peer Dependency? #

It's not that package-a has a "wrong" dependency listed in its package.json. Instead, this warning pops up when:

• You do have the peer dependency installed (so it's not "unmet"),
• But the installed version doesn't fall within the range required by the dependent package.

For example:

• package-a requires package-b@^2.1.5 (any 2.x version ≥2.1.5)
• You have package-b@1.3.0 (too old) or package-b@3.0.0 (too new) installed

This is different from an unmet peer dependency, where no compatible version exists in your project at all.

How to Fix It #

Here are the most common solutions, ordered by how likely they are to resolve the issue:

• Install a compatible version of the peer dependency
  Directly install a version that fits the required range. For example:

  # npm
  npm install package-b@^2.1.5
  # yarn
  yarn add package-b@^2.1.5
  

• Reset your dependency tree
  Sometimes lock files (package-lock.json or yarn.lock) can get stuck with outdated or mismatched version references. Try:

  1. Delete your node_modules folder
  2. Delete your lock file
  3. Run npm install or yarn install again to let the package manager re-resolve dependencies from scratch.

• Upgrade your package manager
  As you noticed, many GitHub issues mention this warning in relation to bugs in npm or yarn. Older versions of these tools sometimes have flaws in their peer dependency resolution logic. Upgrading to the latest stable version can fix these edge cases:

  # Update npm to the latest version
  npm install -g npm@latest
  # Update yarn to the latest stable version
  yarn set version stable
  

Is This a Bug in npm/Yarn? #

Not always. Most of the time, it's just a mismatch between your installed dependencies and what a package requires. However, there are rare cases where the package manager's resolution logic fails to pick a compatible version even when one exists—those are genuine bugs, which is why you see so many reports in their GitHub repos. Always try the first two fixes above before assuming it's a tool bug.

内容的提问来源于stack exchange，提问作者John Pankowicz