| #
d1194e24 |
| 16-Dec-2021 |
Łukasz Kosmaty <[email protected]> |
[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 ✅
show more ...
|
| #
528fde75 |
| 10-Dec-2020 |
Łukasz Kosmaty <[email protected]> |
[expo-dev-manu] Add auto-linking support (#11273)
# Why
We want to make sure that the installation process for `dev-menu` is as trivial as possible. So I've added the auto-linking support into ex
[expo-dev-manu] Add auto-linking support (#11273)
# Why
We want to make sure that the installation process for `dev-menu` is as trivial as possible. So I've added the auto-linking support into expo-dev-menu-interface.
# Test Plan
- bare-expo
- iOS ✅
- Android ✅
show more ...
|