Migrate parts of repo to expo cli (#23806)

feat(cli, metro-config): environment variable support (#21983)

# Why

- It's nice to be able to use uncommitted values in your app, based on
the environment. This feels very familiar to web devel

feat(cli, metro-config): environment variable support (#21983)

# Why

- It's nice to be able to use uncommitted values in your app, based on
the environment. This feels very familiar to web developers.
- Values that are prefixed with `EXPO_PUBLIC_` will be inlined in the
bundle when bundling normally (e.g. not for Node.js).
- `.env` files are loaded into memory and applied to the process during
a run. This also means that they're available in `app.config.js`.
- During development-only, environment variables are exposed on the
`process.env` object (non-enumerable) to ensure they're available
between fast refresh updates.
<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How

- Create new package `@expo/env` which is used to hydrate env variables
in a unified way. I plan to open another PR in `eas-cli` which uses this
package to fill in environment variables before uploading. NOTE:
environment variables that are defined in eas.json are not available in
Expo CLI when building locally, but are available in the cloud since
they'll be on the process, this means they effectively emulate
`.env.production`.
- Update templates to gitignore local env files.
- Add basic documentation to the versioned metro guide (more to come).


<!--
How did you build this feature or fix this bug and why?
-->

# Test Plan

- [ ] E2E rendering test
- [ ] E2E Node.js rendering test
- [x] Unit tests for serializer
- [x] Tests for env package

<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

# 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 ...

[menu] Reimplement the bottom sheet using native languages (#21268)

# Why

Closes ENG-7280.
Reimplemented the bottom sheet using native languages and removed reanimated from vendored modules.
B

[menu] Reimplement the bottom sheet using native languages (#21268)

# Why

Closes ENG-7280.
Reimplemented the bottom sheet using native languages and removed reanimated from vendored modules.
By doing that we improve the build speed.

# How

- On Android, I've used the material design bottom sheet. We may want to copy the implementation from the original repo to ours to avoid extra dependency.
- On iOS, I've copied the implementation from https://github.com/applidium/OverlayContainer. I managed to test a couple of different libraries and that one works the best with RN.

# Test Plan

- bare-expo on both platforms ✅

show more ...

[dev-menu] Update `react-native-gesture-handler` to `2.1.2` (#16371)

# Why

Closes ENG-3990.

# How

Run and adjust our vendoring script for version `2.1.2` of reanimated. Migrate from gesture

[dev-menu] Update `react-native-gesture-handler` to `2.1.2` (#16371)

# Why

Closes ENG-3990.

# How

Run and adjust our vendoring script for version `2.1.2` of reanimated. Migrate from gesture handler root view to the root view component.

# Test Plan

- run `bare-expo` and check if the menu works
- iOS ✅
- Android ✅

show more ...

[expo-dev-launcher] remove SDK 42 compat warning from write_embedded_bundle.sh (#15985)

[dev-client] Fix app js cannot be built

[expo-dev-launcher] add warning to write_embedded_bundle (#14839)

[expo-dev-launcher] Fix bundled images (#12668)

Co-authored-by: Łukasz Kosmaty <[email protected]>

[dev-launcher] Remove from release builds (#11271)

# Why

We don't want to include the `dev-launcher` in the release build.

# How

Similar to https://github.com/expo/expo/pull/10091 and https

[dev-launcher] Remove from release builds (#11271)

# Why

We don't want to include the `dev-launcher` in the release build.

# How

Similar to https://github.com/expo/expo/pull/10091 and https://github.com/expo/expo/pull/10087.

> Note: This PR only contains changes connected to Android. We don't need to do anything else then adding `expo-dev-launcher` as debug dependency on iOS (`pod 'expo-dev-launcher', path: '../../../packages/expo-dev-launcher', :configurations => :debug`)

# Test Plan

- bare-expo (in debug & release) ✅

show more ...

[expo-dev-client] Rename to `expo-dev-launcher` (#11217)

# Why

Rename `expo-dev-client` to `expo-dev-launcher`.

# How

Find & replace ��

# Test Plan

- bare-expo
- iOS ✅
- android

[expo-dev-client] Rename to `expo-dev-launcher` (#11217)

# Why

Rename `expo-dev-client` to `expo-dev-launcher`.

# How

Find & replace ��

# Test Plan

- bare-expo
- iOS ✅
- android ✅

show more ...