[tools] Switch expo home publishing to EAS update (#24216)
[home][ci] Remove dogfood expo home variant (#24193)
[home][tools] Fix detecting home app for dynamic macros (try 2) (#24189)
[tools] Fix detecting home app for dynamic macros (#23583)
Remove Amplitude from Expo Go (#22523)
[gh] Skip fetching local manifest on CI (#20825)# Why Builds on M1 take a long time because generating dynamic macros script hangs for few minutes waiting for a response from local port 80. Pac
[gh] Skip fetching local manifest on CI (#20825)# Why Builds on M1 take a long time because generating dynamic macros script hangs for few minutes waiting for a response from local port 80. Packet filtering rules on EAS Build are dropping all the traffic to the local network, to stop vm to vm communication, which includes requests sent to your own IP. # How I assume generating dynamic macros checks the local port in case that script is run on the developer machine, so skipping that on CI should be safe. If this change is not ok, I can always check for `EAS_BUILD` env there. Another alternative would be to use there 127.0.0.1 ip, but I'm not sure if this would be valid for whatever use case that manifest is needed normally. # Test Plan CI Build time improvement from `34m 51s` to `13m 41s` # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
show more ...
[tools] Avoid dependency on uuid (#20478)
[tools] replace deprecated `request-promise-native` package (#17001)
[tools] add and hook up lint setup, remove `module-scripts` (#16974)
Change several expo.io references to expo.dev or exp.host (#16803)Docs: - Replaced docs.expo.io links in READMEs with docs.expo.dev - Updated references to docs.expo.io throughout docblocks in so
Change several expo.io references to expo.dev or exp.host (#16803)Docs: - Replaced docs.expo.io links in READMEs with docs.expo.dev - Updated references to docs.expo.io throughout docblocks in source code - Updated package.json files that linked to docs.expo.io Emails: - Changed some support and test emails to use `@expo.dev` Classic update hosts: - Changed `exp://expo.io` links to `exp://exp.host` links. This change is consistent with the URLs that Expo CLI generates.
[bare-expo] Make Gradle faster (#15120)# Why Makes Gradle a little bit faster in the `bare-expo` project. # How - Combined `GenerateDynamicMacrosPlugin` and `ExecuteSetupAndroidProject` in
[bare-expo] Make Gradle faster (#15120)# Why Makes Gradle a little bit faster in the `bare-expo` project. # How - Combined `GenerateDynamicMacrosPlugin` and `ExecuteSetupAndroidProject` into one plugin. - Allowed Gradle to run in parallel. - Allowed Gradle to use file watchers to speed up the compilation. - Exclude some unneeded operations from the generating dynamic macros command. - Changed how `setup-android-project.sh` detect RN version. You can check https://proandroiddev.com/how-we-reduced-our-gradle-build-times-by-over-80-51f2b6d6b05b to get more information about some of the optimizations I made. # Test Plan Made several tests involving clean and incremental builds. The biggest gain is in the clean builds - there are two times faster. The incremental builds are also faster, but here the difference is more subtle. We can save about from 4 to 8 seconds. It is not a lot, but still an improvement.
[android] Kotlinize app devicefarm tests (#14161)
[tools] Update ExpoKit podspec after removing SDK version
[client] Add dogfood home build option (#13883)
Refactor uuid imports to v7 style (#13037)
[tools] Move tools/expotools one folder up (#11410)