Skip to content

Commit

Permalink
Upgrading - mention peerDependency on React
Browse files Browse the repository at this point in the history
Summary:
Fixes issues with docs from facebook#11104.

We should document people should update both `react` and `react-native` until we switch to the new upgrades.
Closes facebook#11123

Differential Revision: D4236994

Pulled By: bestander

fbshipit-source-id: 3baf5187eda3701f867e6801632b018d7fe0c1ff
  • Loading branch information
mkonicek authored and Facebook Github Bot committed Nov 28, 2016
1 parent 74c754d commit f2684e3
Showing 1 changed file with 8 additions and 1 deletion.
9 changes: 8 additions & 1 deletion docs/Upgrading.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,11 +20,18 @@ Note the latest version of the `react-native` npm package from here (or use `npm

* https://www.npmjs.com/package/react-native

Now install that version of `react-native` in your project with `npm install --save`.
Now install that version of `react-native` in your project with `npm install --save`:

```sh
$ npm install --save [email protected]
# where X.Y is the semantic version you are upgrading to
npm WARN peerDependencies The peer dependency react@~R included from react-native...
```

If you saw a warning about the peerDependency, also upgrade `react` by running:
```sh
$ npm install --save react@R
# where R is the new version of react from the peerDependency warning you saw
```

## 2. Upgrade your project templates
Expand Down

0 comments on commit f2684e3

Please sign in to comment.