feat(expo): upgrade expo to 47

[xiongemi]

Current Behavior

Expected Behavior

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated
nx-dev	⬜️ Ignored (Inspect)		Dec 2, 2022 at 11:03PM (UTC)

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit eac46de. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 12 targets

• nx affected --target=e2e --base=214c6a317581f2c678ddd003e8ab9fdef484013c --head=eac46deb204e597dac0eea88819f90b6f42d8c08 --exclude=e2e-make-angular-cli-faster,e2e-detox,e2e-js,e2e-next,e2e-workspace-create,e2e-nx-run,e2e-nx-misc,e2e-react,e2e-web,e2e-webpack,e2e-rollup,e2e-esbuild,e2e-angular-extensions,e2e-angular-core,e2e-nx-plugin,e2e-cypress,e2...
• nx affected --target=e2e --base=214c6a317581f2c678ddd003e8ab9fdef484013c --head=eac46deb204e597dac0eea88819f90b6f42d8c08 --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox --parallel=1
• nx affected --target=test --base=214c6a317581f2c678ddd003e8ab9fdef484013c --head=eac46deb204e597dac0eea88819f90b6f42d8c08 --parallel=1
• nx depcheck --no-dte
• nx affected --target=lint --base=214c6a317581f2c678ddd003e8ab9fdef484013c --head=eac46deb204e597dac0eea88819f90b6f42d8c08 --parallel=3
• nx affected --target=build --base=214c6a317581f2c678ddd003e8ab9fdef484013c --head=eac46deb204e597dac0eea88819f90b6f42d8c08 --parallel=3
• nx lint --no-dte
• nx check-lock-files --no-dte
• nx check-commit --no-dte
• nx-cloud record -- nx format:check --base=214c6a317581f2c678ddd003e8ab9fdef484013c --head=eac46deb204e597dac0eea88819f90b6f42d8c08
• nx check-imports --no-dte
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[jaysoo]

LGTM

[yonitou]

Hey !
Seems like you forgot to update the expo version in the peer dependencies of the @nrwl/expo package. When will it be updated ? It's causing issues that make us use --legacy-peer-deps with npm.
Thanks

[xiongemi]

Yes. i forgot to update it. i just submit pr to update it #13780

[Phillip9587]

@xiongemi There was already a PR to update that: #13747

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.