Was confused as to why i was getting this result after running expo-doctor in my project:
And after troubleshooting a bit, and having a talk with AI about it, after sending it a ton of different readouts from npm why etc it ended up saying that it seems like my @convex-dev/expo-push-notifications has mismatch in its depenedencies
I'm fairly sure this doesnt mean i cant export my eas build, as it should be fine. As the component wont ever interfeer with my app native modules.
But i'm sure this would be nice for you guys to know?
The package "expo-modules-autolinking" should not be installed directly in your project. It is a dependency of other Expo packages, which will install it automatically as needed.
Expected package expo-modules-autolinking@~2.0.0
Found invalid:
expo-modules-autolinking@1.11.3
(for more info, run: npm why expo-modules-autolinking)
Expected package @expo/config-plugins@~9.0.0
Found invalid:
@expo/config-plugins@8.0.11
@expo/config-plugins@8.0.11
(for more info, run: npm why @expo/config-plugins)
Expected package @expo/prebuild-config@~8.0.0
Found invalid:
@expo/prebuild-config@7.0.9
(for more info, run: npm why @expo/prebuild-config)
Expected package @expo/metro-config@~0.19.0
Found invalid:
@expo/metro-config@0.18.11
(for more info, run: npm why @expo/metro-config)
Expected package metro@^0.81.0
Found invalid:
metro@0.80.12
(for more info, run: npm why metro)
Expected package metro-resolver@^0.81.0
Found invalid:
metro-resolver@0.80.12
(for more info, run: npm why metro-resolver)
Expected package metro-config@^0.81.0
Found invalid:
metro-config@0.80.12
(for more info, run: npm why metro-config)