it’s adding some packages to package.json and running yarn/npm install. I’m not aware of any other communication, but it’s possible that sth else might be sent there. e.g. expo servers might be contacted to check versions of those packages, but I’m not 100 % sure.
btw code for that is open source you can check there directly GitHub - expo/expo-cli: Tools for creating, running, and deploying universal Expo and React Native apps
expo-cli adds support for this in future.
We created turtle-cli to allow running the same code as our cloud builds on local machines, why would we duplicate the same functionality in expo-cli?
Managed builds by definition can’t be fully offline because you need to have a way to download native code to build it.
- in case of cloud builds we are handling that
- in case of turtle-cli native code is downloaded for the first build and cached (so every next build can be offline)
- in case
expo eject it has to be downloaded on the fly, we could bundle that inside expo-cli but it would have significantly increased the size of the package and made updates more problematic
If you want to have fully offline builds you need to eject and keep the app ejected.