安装BlueprintJS遇未满足对等依赖错误，已装指定依赖求解决方案

Hey there! I know it's frustrating when you've already installed the required dependency but still get that peer dependency warning. Let's walk through some practical steps to get this sorted out:

1. Verify the Installed Version Matches Blueprint's Requirements #

Blueprint 2.0 explicitly requires react-addons-css-transition-group at version ^15.0.1 or ^0.14. First, check what version you actually have installed:

# For npm users
npm list react-addons-css-transition-group

# For yarn users
yarn list react-addons-css-transition-group

If the version isn't in the allowed range, reinstall the correct version that aligns with your React core version (e.g., if you're using React 15.x, go with the 15.x addon):

# For React 15.x
npm install react-addons-css-transition-group@^15.0.1 --save

# For React 0.14.x
npm install react-addons-css-transition-group@^0.14 --save

2. Ensure React and Addon Versions Are Fully Aligned #

The react-addons-css-transition-group version must match your React core version exactly (e.g., React 15.6.2 needs addon 15.6.2). Check your React version first:

npm list react

If there's a mismatch, update either React to match the addon version or vice versa. Keeping them on the same major/minor version is the safest way to avoid compatibility issues.

3. Clean Cache and Reinstall Dependencies #

Sometimes cached node modules or lock files can cause false peer dependency errors. Try a clean reinstall to rule this out:

# Delete node_modules and lock file (npm)
rm -rf node_modules package-lock.json

# For Windows users:
# rmdir /s /q node_modules
# del package-lock.json

# Reinstall dependencies
npm install

If you use yarn, replace the lock file command with rm yarn.lock and reinstall with yarn install.

4. Resolve Nested Dependency Conflicts #

Occasionally, another dependency in your project might be pulling in a different version of react-addons-css-transition-group, causing a hidden conflict. Use the dependency tree to spot this:

npm ls react-addons-css-transition-group

If you see multiple versions listed, try flattening the dependencies first:

npm dedupe

Or, if you're using yarn, add a resolutions field to your package.json to force the correct version:

{
  "resolutions": {
    "react-addons-css-transition-group": "^15.0.1"
  }
}

Then run yarn install again. For npm, you can use the npm-force-resolutions package as a preinstall script to achieve the same forced version lock.

5. Double-Check Local vs. Global Installation #

If you installed Blueprint globally (not recommended for project-specific work), you'll need to install the addon globally too. But for most projects, stick to local dependencies to avoid cross-project version mismatches.

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