Diff for upgrading package.json to 0.61.3 suggests old versions
See original GitHub issueBug
React Native 0.61.3 has a dependency on React 16.9.0 but the upgrade suggestions for 0.61.3 indicate we should use React 16.8.1 (and some other older dependencies)…

React Native versions
0.61.3
Steps to reproduce
Review the suggested diffs for 0.61.3 here
Describe what you expected to happen:
- expect the dependencies to be at least the same as 0.61.3 and same as
react-native initproduces
PS. sorry if I’m missing something obvious - this is my first attempt at using this tool. All assistance is greatly appreciated.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:12 (7 by maintainers)
Top Results From Across the Web
How to update each dependency in package.json to the latest ...
The best way I know is to run npm info express version then update each dependency in package.json manually. There must be a...
Read more >Upgrading React Native from 0.61.5 to 0.62.3 - Medium
Upgrading to new versions of React Native will give you access to more APIs, views, developer tools and other goodies. Upgrading React Native ......
Read more >Upgrading to new versions - React Native
Upgrading to new versions of React Native will give you access to more APIs ... react , and expo package versions in your...
Read more >How to Upgrade Dependencies in Your package.json
After identifying the outdated packages, we fix the version specifications in package.json accordingly. Then we can run npm install or npm update to...
Read more >Why Running `yarn upgrade` Does Not Update My `package ...
The installed version in our node_modules might not be the literal number we see in our package.json . This is because the versions...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

this is something we are fixing. there later versions are the correct ones, but the template and the cli produced this. I would suggest skipping .3 and waiting for .4 which should have the later versions again.
I will close this for now. Let’s revisit after .4 if the problem comes back!