[config][cli] Remove classic manifest types (#24054)

feat(expo)!: drop logging endpoint (#18596)

# Why

- In the new versioned CLI we don't support the logging endpoint,
instead favoring the logging WebSocket setup by `metro-runtime`.
- Dropping s

feat(expo)!: drop logging endpoint (#18596)

# Why

- In the new versioned CLI we don't support the logging endpoint,
instead favoring the logging WebSocket setup by `metro-runtime`.
- Dropping support for `logUrl` will break logging in the legacy
`expo-cli start` command, no logs will show up.
- Drop `Logs` module: `import { Logs } from 'expo';`.
- Drop stack trace filter that removes `react-native-logging.fx` since
we no longer need it.
- Also removes the "temporary workaround"s from 2018 that filter out
warnings from the lottie package.
- Drop direct dependency on `invariant`, `pretty-format`, `fbemitter`

> This doesn't add breaking changes to the local Expo CLI, only the
deprecated global CLI.

# Test Plan

- Copied the JS expo files into a new project and websockets continued
to send logs.

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

---------

Co-authored-by: Expo Bot <[email protected]>

show more ...

feat(cli): dynamically enable lazy bundling (#23675)

# Why

If a package is using `import()` syntax, it needs to have
`@expo/metro-runtime` installed and imported somewhere. This issue
partially

feat(cli): dynamically enable lazy bundling (#23675)

# Why

If a package is using `import()` syntax, it needs to have
`@expo/metro-runtime` installed and imported somewhere. This issue
partially goes away in RN 73, and is not a problem in `expo-router`.

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How

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

# Test Plan

<!--
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 `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

Co-authored-by: Expo Bot <[email protected]>

show more ...

fix(cli): remove invalid "none" platform (#23080)

# Why

- fix regression introduced in https://github.com/expo/expo/pull/19319
- `none` is passed to the bundler and implies the existence of
`.n

fix(cli): remove invalid "none" platform (#23080)

# Why

- fix regression introduced in https://github.com/expo/expo/pull/19319
- `none` is passed to the bundler and implies the existence of
`.none.js` files, and `Platform.select({ none: '...' })` which isn't
valid.
- The default in classic and all other implementations of the metro dev
server has been to fallback on `ios`.
- The most correct variation would be to fallback on `web` as the web is
a non-standard React Native client which doesn't implement the expo
manifest format. However, (metro) web isn't enabled in every project,
and if it were then the JSON manifest would be skipped in favor of the
HTML file.
- remove unneeded logs about offline and anonymous.
- add force-manifest-type options to help prompt.

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How

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

# Test Plan

<!--
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 `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

Co-authored-by: Expo Bot <[email protected]>

show more ...

[cli][packages] unify the default dev server port to 8081 (#22880)

# Why

for historical reasons, when running `npx expo start` the dev-server listens to port 19000, and running `npx expo start --

[cli][packages] unify the default dev server port to 8081 (#22880)

# Why

for historical reasons, when running `npx expo start` the dev-server listens to port 19000, and running `npx expo start --dev-client` it listens to port 8081. since we are now on our effort to deprecate `--dev-client` option, it is better to unify the listening port.
close ENG-8936

# How

- update packages/**/*.ts for port 19000 -> 8081
- search more occurrences for 19000 to 8081

# Test Plan

- ci passed
- bare-expo
- unversioned expo go + ncl

show more ...

feat(cli): add --go option to expo start (#22925)

# Why

We're going to be adding a system to change the default launch mode
based on if dev client is installed. This will enable users to force t

feat(cli): add --go option to expo start (#22925)

# Why

We're going to be adding a system to change the default launch mode
based on if dev client is installed. This will enable users to force the
default behavior in case the default algorithm isn't what they want.
Also adds `-d` alias for dev client, and stops marking `--dev-client` as
experimental.

- Related https://github.com/expo/expo/pull/22924
https://github.com/expo/expo/pull/22890

---------

Co-authored-by: Expo Bot <[email protected]>

show more ...

feat(cli): Add support for Metro lazy bundling (#22724)

# Why

- Companion to https://github.com/expo/router/pull/622

<!--
Please describe the motivation for this PR, and link to relevant GitH

feat(cli): Add support for Metro lazy bundling (#22724)

# Why

- Companion to https://github.com/expo/router/pull/622

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How

- Add `lazy` query parameter for Metro requests and `EXPO_NO_METRO_LAZY`
to disable the feature. Abiding by
https://github.com/react-native-community/discussions-and-proposals/blob/main/proposals/0605-lazy-bundling.md#__loadbundleasync-in-metro

# Test Plan

- Works when used with https://github.com/expo/router/pull/622

---------

Co-authored-by: Expo Bot <[email protected]>

show more ...

[cli] Default to expo go modern manifest format (#22168)

[cli] Fix e2e tests (#22005)

# Why

These are failing in main:
https://github.com/expo/expo/actions/workflows/cli.yml?query=branch%3Amain

Blame seems to be 8fd977ade89c14fcf9229c10eb19590a3c52

[cli] Fix e2e tests (#22005)

# Why

These are failing in main:
https://github.com/expo/expo/actions/workflows/cli.yml?query=branch%3Amain

Blame seems to be 8fd977ade89c14fcf9229c10eb19590a3c52c80b. No idea why
that changes these or what these are testing but meh.

# How

Update tests.

# Test Plan

`yarn test:e2e`

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

feat(cli): add basic static rendering for router projects (#21572)

# Why

- Implement an experimental static rendering system for Metro websites
using Expo Router.
- Behavior is undocumented and

feat(cli): add basic static rendering for router projects (#21572)

# Why

- Implement an experimental static rendering system for Metro websites
using Expo Router.
- Behavior is undocumented and highly experimental.

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How

- Add support to `start` and `export` which pre-renders static web pages
to HTML to improve SEO support on web.
- The system implements [React Navigation's
SSR](https://reactnavigation.org/docs/server-rendering) support.
- Head elements can be used with `import { Head } from
'expo-router/head'`.
- The root HTML is not exposed to the user.
- There are no data fetching mechanisms.
- There's no ability to provide a 404 page or other server features.


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

# Test Plan

- e2e test for exporting a router project statically.
- `EXPO_USE_STATIC=1 yarn expo` -> websites are pre-rendered before
being served.
- `EXPO_USE_STATIC=1 yarn expo export -p web` -> static routes are
rendered to static HTML files by the same name (dynamic routes are not
supported).


<!--
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).

---------

Co-authored-by: Expo Bot <[email protected]>

show more ...

chore(cli): fix e2e tests (#21335)

- upgrade CLI e2e tests to SDK 47
- upgrade webpack to v5

---------

Co-authored-by: Expo Bot <[email protected]>

[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

show more ...

feat(cli): add web support to metro (#17927)

* feat: add web support for metro

* undo patch

* Update index.js

* Update MetroBundlerDevServer.ts

* Add second bundler dev server

* Add d

feat(cli): add web support to metro (#17927)

* feat: add web support for metro

* undo patch

* Update index.js

* Update MetroBundlerDevServer.ts

* Add second bundler dev server

* Add dev loading view to web

* Put feature behind EXPO_USE_METRO_WEB flag

* Move custom config into CLI

* Add support for assets across platforms

* reduce

* Added upstream web support

* Update webTemplate.ts

* Update CHANGELOG.md

* Update instantiateMetro.ts

* Update instantiateMetro.ts

* Update index.js

* Added bundle splitting support

* Update startAsync.ts

* Fixed default settings

* Add ability to copy from public folder

* wip: redirect unmatched routes to `/` on web

* fix fallback api

* Update exportApp.ts

* Update instantiateMetro.ts

* Update exportApp.ts

* clean up handler

* fixup

* clean up

* add web to export test

* Update start-test.ts

* added static serving for web

* Update packages/@expo/cli/CHANGELOG.md

Co-authored-by: Expo Bot <[email protected]>

* Update yarn.lock

lint fix

fix tests

* Update export-test.ts

* added template tests

* Create HistoryFallbackMiddleware-test.ts

* test ManifestMiddleware

* Create ServeStaticMiddleware-test.ts

* refactor multiplatform

* Update ManifestMiddleware-test.ts

* Update withMetroMultiPlatform.ts

* Update for latest metro

* Update packages/@expo/cli/src/export/resolveOptions.ts

Co-authored-by: Expo Bot <[email protected]>

show more ...

chore(cli): update test fixtures to SDK 45 (#17934)

* chore(cli): update test fixtures to SDK 45

* updated tests

* Update packages/@expo/cli/CHANGELOG.md

Co-authored-by: Expo Bot <34669131+

chore(cli): update test fixtures to SDK 45 (#17934)

* chore(cli): update test fixtures to SDK 45

* updated tests

* Update packages/@expo/cli/CHANGELOG.md

Co-authored-by: Expo Bot <[email protected]>

* Update start-test.ts

Co-authored-by: Expo Bot <[email protected]>

show more ...

feat(cli): redesign cli help interface (#17223)

* redesign cli help interface

* Update CHANGELOG.md

* Update index.ts

* Update packages/@expo/cli/CHANGELOG.md

Co-authored-by: Expo Bot <3

feat(cli): redesign cli help interface (#17223)

* redesign cli help interface

* Update CHANGELOG.md

* Update index.ts

* Update packages/@expo/cli/CHANGELOG.md

Co-authored-by: Expo Bot <[email protected]>

* Updated export

* updated the export

Co-authored-by: Expo Bot <[email protected]>

show more ...

fix(cli): update login error message to reflect server change (#16932)

* fix(cli): update login error message to reflect server change

* Update CHANGELOG.md

* Update login-test.ts

* Update

fix(cli): update login error message to reflect server change (#16932)

* fix(cli): update login error message to reflect server change

* Update CHANGELOG.md

* Update login-test.ts

* Update packages/@expo/cli/CHANGELOG.md

Co-authored-by: Expo Bot <[email protected]>

* Update start-test.ts

Co-authored-by: Expo Bot <[email protected]>

show more ...

feat(cli): add development code signing (#16845)

chore: refactor `expo/cli` to `@expo/cli` package (#16717)

* chore: refactor `expo/cli` to `@expo/cli` package

* Update CODEOWNERS

* fix linking

* fix lint script

* fix build file

* f

chore: refactor `expo/cli` to `@expo/cli` package (#16717)

* chore: refactor `expo/cli` to `@expo/cli` package

* Update CODEOWNERS

* fix linking

* fix lint script

* fix build file

* fix e2e tests

* lint before build

* use mock version

show more ...