You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EAS CLI executes the @expo/cli in an interesting way, which seems incompatible with isolated modules. TL;DR;
When EAS CLI needs to execute the Expo CLI, it fully resolves the path to the binary.
When the binary path is resolved, it executes it directly (e.g. /<path>/node_modules/<expo-path>/bin/cli)
This seems to be incorrect when using isolated modules, as this changes the accessible context from "all node_modules which are installed in the project" to "only node_modules of expo"
This method of interacting with the Expo CLI seems not correct, as users would normally use it like:
Summary
EAS CLI executes the
@expo/cli
in an interesting way, which seems incompatible with isolated modules. TL;DR;/<path>/node_modules/<expo-path>/bin/cli
)node_modules
which are installed in the project" to "onlynode_modules
ofexpo
"This method of interacting with the Expo CLI seems not correct, as users would normally use it like:
bun expo export ...
yarn expo export ...
npx expo export ...
pnpm expo export ...
What platform(s) does this occur on?
Android, iOS, Web
SDK Version
50.0.0
Environment
Minimal reproducible example
$ git clone [email protected]:byCedric/expo-monorepo-example.git ./issue-2150
$ cd ./issue-2150
$ git checkout issues/eas/2150
$ pnpm install
$ cd apps/mobile
$ eas update --branch issue-eas-2150 --message "Test issue 2150"
The above command sequence fails with the error listed above.
The text was updated successfully, but these errors were encountered: