Deprecate source-login-scripts.sh (#18330)

# Why

the `source-login-scripts.sh` introduced a lot of pain where the community reported much build errors from it. it doesn't support shells other tha

Deprecate source-login-scripts.sh (#18330)

# Why

the `source-login-scripts.sh` introduced a lot of pain where the community reported much build errors from it. it doesn't support shells other than zsh and bash. this pr find a new way to deal with xcode building issues that it cannot find the correct nodejs path.

close ENG-4864
close ENG-5242

# How

react-native introduces `.xcode.env` and `.xcode.env.local` for developers to override the `$NODE_BINARY`: https://github.com/facebook/react-native/pull/33546

to make sure building success from expo-constants, expo-updates, and also the app target when generating bundles. i would like to reuse the `.xcode.env` and `.xcode.env.local` from react-native. this pr further generates `.xcode.env.local` automatically for the app during `pod install`. we can ensure that `pod install` is executed from shell and nodejs is available. so we will generate `export NODE_BINARY="$(command -v node)"` in the `.xcode.env.local`. for xcode, the path will be `$PODS_ROOT/../.xcode.env.local`, every xcode subprojects can source the file to get correct `$NODE_BINARY`.

# Test Plan

- building bare-expo from xcode (opening xcode by macos finder)
- building bare-expo by `yarn ios`
- updates e2e ci passed
- building expo-go (prerequisite: #18344)

Co-authored-by: James Ide <[email protected]>

show more ...

[module-scripts] Fix source-login-scripts.sh be generated in other expo modules (#15376)

# Why

regression of #15336, where we should not sync `source-login-scripts.sh` to other expo modules.
i j

[module-scripts] Fix source-login-scripts.sh be generated in other expo modules (#15376)

# Why

regression of #15336, where we should not sync `source-login-scripts.sh` to other expo modules.
i just misread the `if [ ! -f "$output_file" ] || grep --quiet "@generated" "$output_file"; then` line.

# How

- introduce `source-login-scripts.sh` as an optional template file which only to sync if it's present and contains `@generated` as described in https://github.com/expo/expo/pull/15336#discussion_r758905459

# Test Plan

- `yarn prepare` in expo-device and make sure `source-login-scripts.sh` not be generated.
- change `source-login-scripts.sh` and `yarn prepare` in expo-constants. check it's updated.


Co-authored-by: James Ide <[email protected]>

show more ...

[module-scripts] vendoring source-login-scripts.sh (#15336)

# Why

follow up with https://github.com/expo/expo/pull/14895#issuecomment-953428185
close ENG-2493

# How

add `templates/scripts/

[module-scripts] vendoring source-login-scripts.sh (#15336)

# Why

follow up with https://github.com/expo/expo/pull/14895#issuecomment-953428185
close ENG-2493

# How

add `templates/scripts/source-login-scripts.sh` to expo-module-scripts and it will sync to expo module package when `yarn prepare` if there's also `scripts/source-login-scripts.sh` and having `@generated` comment mark.

change the file iterator in `expo-module-configure` from shell glob expansion with `find` which enabled the recursive iteration, e.g. `scripts/source-login-scripts.sh`

# Test Plan

- modify some template files in expo-module-scripts and `yarn prepare` for `expo-constants`, make sure the files are synced.
- `yare prepack` in expo-updates and from a sdk43 project to run `yarn add file:/path/to/expo/packages/expo-updates`, test the build successful.

show more ...

Updating READMEs and docs for unimodules and other related changes (#3558)

* Project lifecycle changes and some other cleanup

* A bunch of incremental improvements

* Make section groups and ha

Updating READMEs and docs for unimodules and other related changes (#3558)

* Project lifecycle changes and some other cleanup

* A bunch of incremental improvements

* Make section groups and have them be collapsable

* Group API reference too

* Shuffle docs a bit for grouping

* Tweak styles

* Reorder a few things in fundamentals and fix AppAuth name

* Create a bare workflow group

* Add consistent sections for installation and api to sdk

* Remove expo-core from dependencies

* Add expo-module script for generating README

* Add some helpful links to footer

* Update website in unimodules to point to docs

* Update READMEs

* Backport docs changes and a few small changes

* Backport more docs from unversioned

* Fix broken links

* Fix some more links

* Move peerDependencies on unimodule packages to unimodulesPeerDependencies
Also move some direct dependencies on unimodule packages to
unimodulesPeerDependencies. This field is currently unused, but
peerDependencies does not work with transitive dependencies so users
will get a lot of warnings and they won't be particularly helpful. Version
changed to * for now because it's unused and I'm not sure everything is
up to date anyhow.

* Add note about scoping in expo-font

* Update unimodule packages to 3.0

* Add Hello World doc

show more ...

Release SDK32 (#3101)

* [tools-public] fix generate-dynamic-macros-android.sh

* [sdk] bump react-native-reanimated JS version to 1.0.0-alpha.11

* [ncl] add missing setMinimumIntervalAsync call

Release SDK32 (#3101)

* [tools-public] fix generate-dynamic-macros-android.sh

* [sdk] bump react-native-reanimated JS version to 1.0.0-alpha.11

* [ncl] add missing setMinimumIntervalAsync call to background fetch example

* [packages] Do not publish babel.config.js in universal modules (#3099)

# Why

With `babel.config.js` published inside the packages, Jest transpiles their source code with included configuration (which isn't, and isn't supposed to be, valid outside of Expo monorepo).

# How

Added `.npmignore` file, excluding `babel.config.js` to `expo-module-scripts/templates`, ran:

```sh
# in packages
for package in ./*; do pushd $package; yarn; popd; done
```

# Test Plan

- [x] Publish prerelease packages
- [x] Confirm that tests work now out of the box

* [expokit-npm-package] bump version to v32.0.0

* [fastlane] fix `open` function throwing error when trying to open from uri

* Publish SDK32

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

* [jest-expo] Publish [email protected]

* [expokit] Update for final SDK32 (#3107)

* [expokit] Update for final SDK32

* [expokit] Publish [email protected]

* [expokit] Publish [email protected]

* [wip][docs] Update (#3108)

[docs] add Android ExpoKit upgrade steps and missing docs for notification categories

* Update CHANGELOG.md

Co-Authored-By: tsapeta <[email protected]>

show more ...

[ts] Add TypeScript+Jest to expo-module-scripts and migrate expo-sms to TS

expo-module-scripts now includes a base tsconfig.base.json file and a base babel.config.base.js file for all unimodules in

[ts] Add TypeScript+Jest to expo-module-scripts and migrate expo-sms to TS

expo-module-scripts now includes a base tsconfig.base.json file and a base babel.config.base.js file for all unimodules in this repo. This ensures that we can make a change to tsconfig.base.json and have it apply to all packages so that our attention is not split across multiple different tsconfig files.

expo-module-scripts also sets up ts-jest and configures TypeScript and Babel to run as part of Jest tests. During Jest tests, Jest will use ts-jest to compile TS to ES2018 JS. Then it will use Babel to compile ES2018 JS using babel-preset-expo -- this matches the same transform as used for devices, helping us verify that the preset does not introduce bugs into our modules.

Because the Jest tests run Babel, we need a Babel configuration file in each module. To keep things simple, I added a one-line configuration file that refers back to expo-module-scripts. This way, we have one source of truth for all unimodules.

Test plan: Ran `yarn build` and `yarn test` in the expo-sms package.

show more ...