-
Notifications
You must be signed in to change notification settings - Fork 24.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Upgrade React and React Native at the same time
Summary: **Motivation** As NoelBroda pointed out in #11104 and #11123, NPM often produces an unmet peerDependency when upgrading React Native. It causes a failure when running "npm install" with NPM2. During the git-upgrade, we have to take care of the `react` peerDep: this PR checks if the installed `react` package matches the `react` peerDep of the new `react-native` version. If so, R & RN are upgraded at the same time (in the same `npm install`). **Test plan** - Publish `react-native-git-upgrade` to Sinopia, - Run `react-native-git-upgrade` inside a RN project with version < 0.37, - Verify that no "unmet peer dependency" warning is displayed - Open the `package.json` and verify that both R & RN have been updated Closes #11226 Differential Revision: D4258007 Pulled By: mkonicek fbshipit-source-id: cff466d4710807d97fc6161f47bb974097b75261
- Loading branch information
Showing
1 changed file
with
29 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Is this considering
yarn
use? package.json doesn't change in yarn on upgrades, only yarn.lock changes.