[menu][Android] Rewrite safe area view using new API (#21609)
[dev-launcher][iOS] Migrate to new modules API (#22319)# Why In order to add support for Fabric to expo-dev-client and related libraries we must migrate all related modules to the new API Re
[dev-launcher][iOS] Migrate to new modules API (#22319)# Why In order to add support for Fabric to expo-dev-client and related libraries we must migrate all related modules to the new API Related to ENG-7955 # How Migrate EXDevLauncher classes to use the new modules API # Test Plan Run dev client through bare expo <table> <tr> <td> <img src="https://user-images.githubusercontent.com/11707729/235227186-5d5ebcd7-7739-4af5-86e9-1d156304e582.png" /> </td> <td> <img src="https://user-images.githubusercontent.com/11707729/235227365-bb1deb30-ccf4-45b2-8416-0f6992bf5135.png" /> </td> </tr> </table> # 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 `npx expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Gabriel Donadel <[email protected]>
show more ...
[menu][ios] Rewrite safe area view using new API (#22174)# Why In order to add support for Fabric to expo-dev-client and related libraries we must migrate all non-fabric compatible libraries to
[menu][ios] Rewrite safe area view using new API (#22174)# Why In order to add support for Fabric to expo-dev-client and related libraries we must migrate all non-fabric compatible libraries to the new API Related to ENG-7955 # How Rewrite safe area view using new API # Test Plan Run dev client through bare expo  # 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).
[2/3] upgrade react native 0.71 (#20832)# Why follow up #20799 for react-native 0.71 upgrade. this pr aims for jest upgrade and fix all broken tests. close ENG-7192 # How - upgrade packag
[2/3] upgrade react native 0.71 (#20832)# Why follow up #20799 for react-native 0.71 upgrade. this pr aims for jest upgrade and fix all broken tests. close ENG-7192 # How - upgrade packages - `jest: ^26.0.24 -> ^29.2.1` - `jest-watch-typeahead: 0.6.4 -> 2.2.1` - `@types/jest: ^26.0.24 -> ^29.2.1` - `babel-jest: ^26.6.3 -> ^29.2.1` - `@jest/create-cache-key-function: ^27.0.1 -> ^29.2.1` - `@babel/preset-env: ^7.12.9 -> ^7.14.0` - `eslint: ^8.20.0 -> ^8.29.0` - add `jest-environment-jsdom` because new jest does not include it by default - [core] fix `SyntheticPlatformEmitter` type error. originally it refers to `react-native/Libraries/EventEmitter/RCTDeviceEventEmitter` internal file which has incorrect type setup in 0.71. we could use the `react-native.DeviceEventEmitter` instead. - [expo-linking]: remove the deprecated `Linking.removeEventListener` (which is also removed from upstream) - [firebase-recaptcha] remove broken web test because firebase ESM which is not supported by jest. this pr simply remove the test case because the package is deprecated. - [jest-expo-enzyme] remove this package and move to [the archived repo](https://github.com/expo/jest-expo-enzyme). enzyme cannot upgrade to jest 29. - remove `@types/react-native` and the versioned cli package check. because 0.71 ships the types directly. - [ncl] workaround `@react-native-community/slider`, `@react-native-segmented-control/segmented-control`, and `@react-native-masked-view/masked-view` type errors in the `react-native-71-fix.d.ts`. - for other details, please check the commit histories one by one. # Test Plan - ci passed - for test-suite ios ci error, i've mentioned in #20799
[dev-client] Move podspecs to the root directory (#15580)# Why The decision to move `dev-menu` and `dev-launcher` podspecs to the `ios` directory wasn't great. Thanks to https://github.com/exp
[dev-client] Move podspecs to the root directory (#15580)# Why The decision to move `dev-menu` and `dev-launcher` podspecs to the `ios` directory wasn't great. Thanks to https://github.com/expo/expo/pull/15578, we will be able to leave podspecs in the root directory. Why this is handy: > It's very hard to resources between iOS and Android when you can't point to local files located above the podspec file. Unfortunately, cocoapods in that place doesn't support paths that aren't in the same directory as podspec. Moreover, it will reduce migration headaches. Currently, users have in theirs Podfiles references to pod pointed to the package directory. It also fixes a compilation error in the `bare-expo` - cannot find `devmenu.com.th3rdwave.safeareacontext.SafeAreaContextPackage`. # How - Moved podspecs - Moved vendored code outside of the ios folder - Removed unused xcproj - Ensured that our modules can't be linked by RN # Test Plan - bare-expo ✅
[dev-launcher] update RN app (#15343)
[dev-menu] vendor react-native-safe-area-context (#15382)