Update tsconfigs to node 18 (current LTS) (#24471)

# Why

Expo supports Node.js LTS, this is currently Node 18. This PR updates
from 14 to 18.

<!--
Please describe the motivation for this PR,

Update tsconfigs to node 18 (current LTS) (#24471)

# Why

Expo supports Node.js LTS, this is currently Node 18. This PR updates
from 14 to 18.

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

---------

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

show more ...

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

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

feat(cli): improve offline support (#22961)

# Why

Offline support is sometimes needed in parts of other commands besides
`start`, this PR introduces an `EXPO_OFFLINE` env var which can be
gener

feat(cli): improve offline support (#22961)

# Why

Offline support is sometimes needed in parts of other commands besides
`start`, this PR introduces an `EXPO_OFFLINE` env var which can be
generally used to force offline support.
<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How

- `EXPO_OFFLINE`
- Show a better error message when your computer is connected to wifi
but there's no signal.
- Assert in `npx expo login` and `npx expo register` when `EXPO_OFFLINE`
is set.
- Fail better when validating versions offline.

In the case of running `npx expo` without wifi:

## Before

```
june-16 �� nexpo
Starting project at /Users/evanbacon/Documents/GitHub/lab/june-16
Starting Metro Bundler
Unable to reach Expo servers. Falling back to using the cached dependency map (bundledNativeModules.json) from the package "expo" installed in your project.
FetchError: request to https://api.expo.dev/v2/versions/latest failed, reason: getaddrinfo ENOTFOUND api.expo.dev
FetchError: request to https://api.expo.dev/v2/versions/latest failed, reason: getaddrinfo ENOTFOUND api.expo.dev
at ClientRequest.<anonymous> (/Users/evanbacon/Documents/GitHub/expo/node_modules/node-fetch/lib/index.js:1491:11)
at ClientRequest.emit (node:events:513:28)
at TLSSocket.socketErrorListener (node:_http_client:502:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
```

## After

```
june-16 �� nexpo
Starting project at /Users/evanbacon/Documents/GitHub/lab/june-16
Starting Metro Bundler
Unable to reach Expo servers. Falling back to using the cached dependency map (bundledNativeModules.json) from the package "expo" installed in your project.
CommandError: Network connection is unreliable. Try again with the environment variable `EXPO_OFFLINE=1` to skip network requests.
```


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

# Test Plan

- Updated tests and added new tests for things like the register
command.

---------

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

Add `--reset-cache` flag to `expo start` and `expo export` for interop with the Metro docs. (#22589)

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

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