Fix react-addons-update package name

(cherry picked from commit cb5913a842)
This commit is contained in:
Ben Alpert
2015-07-04 17:26:57 +02:00
parent 52c9efedb3
commit 4e1918d4ea
+1 -1
View File
@@ -38,7 +38,7 @@ We anticipate that most components will need to depend only on the `react` packa
More importantly, this paves the way to writing components that can be shared between the web version of React and React Native. This isn't yet easily possible, but we intend to make this easy in a future version so you can share React code between your website and native apps.
The addons have moved to separate packages as well: react-addons-clone-with-props, react-addons-create-fragment, react-addons-css-transition-group, react-addons-linked-state-mixin, react-addons-pure-render-mixin, react-addons-shallow-compare, react-addons-transition-group, and react-addons-updates, plus `ReactDOM.unstable_batchedUpdates` in react-dom.
The addons have moved to separate packages as well: react-addons-clone-with-props, react-addons-create-fragment, react-addons-css-transition-group, react-addons-linked-state-mixin, react-addons-pure-render-mixin, react-addons-shallow-compare, react-addons-transition-group, and react-addons-update, plus `ReactDOM.unstable_batchedUpdates` in react-dom.
For now, please use the same version of `react` and `react-dom` in your apps to avoid versioning problems -- but we plan to remove this requirement later. (This release includes the old methods in the `react` package with a deprecation warning, but they'll be removed completely in 0.15.)