Meteor应用安装React后崩溃：版本兼容及react-addons-transition-group问题

Hey there, let’s work through this problem step by step—this is a super common gotcha with older Meteor React setups, so we’ll get you sorted.

Why You’re Seeing These Errors #

First, let’s demystify the two issues:

• React version conflicts: Older versions of Meteor’s official react package (installed via meteor add react) lock you into a specific React version. If you manually installed the latest react/react-dom via npm, you’re creating a mismatch between Meteor’s managed version and your npm-installed one.
• react-addons-transition-group requirement: This package was part of React’s old "addons" ecosystem, which has been deprecated for years. Modern React moved these transition components into the standalone react-transition-group package, but older Meteor React integrations still reference the old addon path.

Step-by-Step Fixes #

1. Resolve Version Conflicts #

First, align your React versions properly:

• If you’re using Meteor’s built-in react package (check with meteor list), uninstall your npm-installed React:

  npm uninstall react react-dom
  

  Meteor will handle providing the correct React version compatible with its integration.
• If you want to use a specific React version (e.g., React 16.x for older Meteor setups), run meteor show react to see the supported version, then install it via npm:

  npm install react@<your-meteor-supported-version> react-dom@<your-meteor-supported-version>
  

2. Replace the Deprecated Transition Package #

Forget about react-addons-transition-group—it’s no longer maintained. Instead:

• Install the modern replacement:

  npm install react-transition-group
  

• Update all imports in your codebase from the old addon to the new package:

  // Before (deprecated)
  import TransitionGroup from 'react-addons-transition-group';
  
  // After (modern)
  import { TransitionGroup } from 'react-transition-group';
  

  The API is mostly identical, but double-check custom transition logic for minor compatibility tweaks if needed.

3. Clear Meteor’s Cache #

Meteor can hold onto old dependency caches that cause weird issues. Run this to reset everything:

meteor reset

Then restart your app with meteor run.

4. Long-Term: Upgrade Meteor (If Possible) #

If you want to use newer React versions (17+ or 18), upgrade your Meteor instance to a compatible version:

• Meteor 2.0+ supports React 17
• Meteor 2.5+ supports React 18
  Once upgraded, you can remove the Meteor react package entirely and rely solely on npm-installed react/react-dom for full version control.

Final Check #

After making these changes, run meteor npm ls react react-dom react-transition-group to verify all versions are aligned and no duplicate packages are installed.

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