Expo doctor looks ok:
┌─────────────────────────────────────────────────────────────────────────┐
│ │
│ There is a new version of expo-cli available (5.4.12). │
│ You are currently using expo-cli 5.4.11 │
│ Install expo-cli globally using the package manager of your choice; │
│ for example: npm install -g expo-cli to get the latest version │
│ │
└─────────────────────────────────────────────────────────────────────────┘
Found all copies of expo-modules-autolinking
All copies of expo-modules-autolinking satisfy ~0.8.1 || ~0.9.0
Found all copies of @expo/config-plugins
All copies of @expo/config-plugins satisfy ^4.1.0
Found all copies of @expo/prebuild-config
All copies of @expo/prebuild-config satisfy ^4.0.0
You should not have expo-cli installed as a devDependency (or dependency). It should be installed globally instead.
If I run expo doctor now, with your dependencies/devDependencies it complains about @expo/config-plugins@5.0.0. This appears to be a bug. I’m not sure if it’s a bug in expo doctor or in dependency versions of some Expo packages.
Do you need this?
These look to me like they should be devDependencies, rather than dependencies, although I’m not sure how much difference it actually makes.
I ran expo install on a bunch of the expo packages and there were some minor changes. I also removed the expo-cli and @expo/metro-config dependencies and it builds for me.