expo diagnostics Expo CLI 4.12.1 environment info: System: OS: Windows 10 10.0.21390 Binaries: Node: 14.16.1 - C:\Program Files\nodejs\node.EXE npm: 6.14.12 - C:\Program Files\nodejs\npm.CMD IDEs: Android Studio: Version 220.127.116.11 AI-202.7618.104.22.16851085 npmPackages: expo: ~41.0.1 => 42.0.4 react: 16.13.1 => 16.13.1 react-dom: 16.13.1 => 16.13.1 react-native: https://github.com/expo/react-native/archive/sdk-41.0.0.tar.gz => 0.63.2 react-native-web: ~0.13.12 => 0.13.18 Expo Workflow: managed
Hello people, so I just got back on a project I worked on for a few months at the beginning of the year and I had to put aside for a moment to help someone complete another one. I would like to get back to it in the best possible way, so I thought first I will upgrade all my packages. Of course expo first -
expo upgrade is a no brainer. But then I got a lot of other packages. React navigation for example that got to its v5 while I have v5 installed, and such.
So I looked for a good way to handle upgrading all those packages, found ncu, looks cool but I’m not sure how it would handle compatibility (even more so in an expo project).
Maybe I should simply create a new fresh expo project, copy over my src code and whatever I wrote, and
expo install any needed dependency again? But I thought there should be a simpler way.