One of the updates in Expo 46 was to make @expo/cli package a locally installed bin package and remove the need to globally install expo-cli per this blog announcement. Here is the warning provided by expo-cli anytime it is run:
This command is being executed with the global Expo CLI. Learn more: https://blog.expo.dev/the-new-expo-cli-f4250d8e3421
To use the local CLI instead (recommended in SDK 46 and higher), run:
› npx expo start
@expo/cli is a dependency of the expo@46.x.x package so it will always be installed and available.
Even better, it is tied to the version of the Expo SDK that you are running unlike expo-cli which maintains a compatible version with all previous versions of the Expo SDK (further bloating it).
Unfortunately, when I attempt to remove expo-cli from my project, none of the executors will run as they cannot find the expo-cli package.
Please change the dependencies in the @nrwl/expo package to use the new @expo/cli to get ahead of the deprecation of the global expo-cli package in the upcoming versions of the Expo SDK.
One of the updates in Expo 46 was to make
@expo/cli
package a locally installed bin package and remove the need to globally installexpo-cli
per this blog announcement. Here is the warning provided byexpo-cli
anytime it is run:@expo/cli
is a dependency of theexpo@46.x.x
package so it will always be installed and available.Even better, it is tied to the version of the Expo SDK that you are running unlike
expo-cli
which maintains a compatible version with all previous versions of the Expo SDK (further bloating it).Unfortunately, when I attempt to remove
expo-cli
from my project, none of the executors will run as they cannot find theexpo-cli
package.Please change the dependencies in the
@nrwl/expo
package to use the new@expo/cli
to get ahead of the deprecation of the globalexpo-cli
package in the upcoming versions of the Expo SDK.