feat(cli): Enable tsconfigPaths by default (#24490)

# Why

ENG-9888

# How

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

# Test Plan

<!--
Please describe how you t

feat(cli): Enable tsconfigPaths by default (#24490)

# Why

ENG-9888

# 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]>
Co-authored-by: Aman Mittal <[email protected]>

show more ...

feat: separate Expo Web & Metro types from router (#24255)

# Why

[ENG-9978
](https://linear.app/expo/issue/ENG-9978/split-the-typed-environment-feature-out-of-typed-routes)

Expo Router includ

feat: separate Expo Web & Metro types from router (#24255)

# Why

[ENG-9978
](https://linear.app/expo/issue/ENG-9978/split-the-typed-environment-feature-out-of-typed-routes)

Expo Router included TypeScript definitions for Expo Web and Metro. I'm
not 100% sure the best place to move these types too, so I'm open to
suggestions.

`expo` for Expo Web, as there is no Expo Web package and these are
global environment types.
`@expo/metro-config`. Its a bit weird putting these types in the config
package, but this is also where a lot of the related code is.

# 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(router): correctly clone hoisted groups (#24218)

# Motivation

Fixes: https://github.com/expo/router/issues/805

Hoisted routes inside array groups were not being correctly cloned. The
matc

fix(router): correctly clone hoisted groups (#24218)

# Motivation

Fixes: https://github.com/expo/router/issues/805

Hoisted routes inside array groups were not being correctly cloned. The
matcher was not detecting the hoisted route and the cloning logic
assumed one set of groups, but a hoisted route may have many.

# Execution

* Updated `matchGroupName` regex to allow for leading/trailing folder
names.
* Updated `fileNodeToRouteNode` logic to extrapolate multiple array
groups

# Test Plan

Modified the example in https://github.com/expo/router/issues/805 to
include a set of nested groups as well.

File tree is

```
events/_layout // <Slot />
events/(manage,preview)/_layout // <Slot />
events/(manage,preview)/[eventId]
events/(manage,preview)/(a,b)/_layout // <Slot />
events/(manage,preview)/(a,b)/test
```

Current (2.0.4) Sitemap:

![localhost_8081__sitemap
(1)](https://github.com/expo/router/assets/3946701/e32d867f-055f-40f5-a25f-94113e39c40b)

After:



---------

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

show more ...

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

feat(cli): Improve truncated Metro Node.js errors. (#24546)

# Why

Split errors by lines and measure to ensure we're only tested against
libraries with one really long line.

---------

Co-au

feat(cli): Improve truncated Metro Node.js errors. (#24546)

# Why

Split errors by lines and measure to ensure we're only tested against
libraries with one really long line.

---------

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

show more ...

feat(cli): reduce static group routes (#24529)

# Why

- In server mode, we don't need to export every group variation because
the server can automatically delegate all matchable paths to the sing

feat(cli): reduce static group routes (#24529)

# Why

- In server mode, we don't need to export every group variation because
the server can automatically delegate all matchable paths to the single
group file.
- This change only exports one static HTML file for a given group route
when server mode is used in export, this can drastically reduce the
amount of output files.


# Test Plan

- Added an e2e test to ensure the path variation is served as expected.

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

router v3 public fixes (#24472)

# Why

- Some small fixes for Expo Router v3 based on the alpha release

---------

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

[RFC] API Routes in Expo Router (#24429)

# Why

Servers are an important part of developing many different types of
apps, but they're much harder to configure than they need to be.

API Routes

[RFC] API Routes in Expo Router (#24429)

# Why

Servers are an important part of developing many different types of
apps, but they're much harder to configure than they need to be.

API Routes will enable users to express some abstract JavaScript code
that runs in a server by simply creating a file in the app directory,
and adding the `+api.js` suffix. For example, to securely interact with
OpenAI, simply:

```ts
// app/generate+api.ts
import { ExpoRequest, ExpoResponse } from 'expo-router/server';

export async function POST(req: ExpoRequest): Promise<ExpoResponse> {
const { prompt } = await req.json();

const json = await fetch('https://api.openai.com/v1/engines/text-davinci-003/completions', {
headers: {
'Content-Type': 'application/json',
// `OPENAI_API_KEY` is pulled from the .env file when running in Expo CLI.
Authorization: `Bearer ${process.env.OPENAI_API_KEY ?? ''}`,
},
method: 'POST',
body: JSON.stringify({
prompt,
max_tokens: 100,
}),
}).then(res => res.json());

// Return as JSON
return ExpoResponse.json(json);
}
```

This will be served at `http://localhost:8081/generate` with `npx expo`
and can be used by making a request:

```sh
$ curl -X POST -H "Content-Type: application/json" -d \'{"prompt":"Hello, my name is"}\' http://localhost:8081/generate
```

Expo Router polyfills the URL and `window.location` object on native to
allow for universally requesting with a relative URL:

```js
// Expo prepends the host and port to the URL automatically in development.
const json = await fetch('/generate').then(res => res.json());
```

# How

- API Routes are bundled with Metro, leveraging all the same
functionality as the rest of the app and website.
- The project babel config is used to transpile the API routes.
Indication is passed to the Babel caller via the `isServer` boolean.
This can be used to change the preset based on the environment.
- Each API route is bundled into a standalone file in the `dist/_expo`
directory. This is akin to ncc, the tool we use to make Create Expo App
download in ~1 second.
- Create a new package `@expo/server` which includes the requisite
middleware and runtime polyfills for the Expo server environment.
- Add a new routes manifest which will be used by `@expo/server` to
serve up the three types of routes: HTML routes, API routes, and not
found routes (404s).
- Add a new export `expo-router/server` (potentially will be moved to
`expo/server`) which contains the `ExpoRequest` and `ExpoResponse`
objects. These are all based on the WinterCG specification, and include
some additional properties for interop with the Expo Router filesystem
convention. These are inspired by Remix, SvelteKit, and Next.js for
simplicity.
- Add a new export mode `web.output: "server"` which can be used to
export a dynamic server. Note: I may drop this for now and make server
the default since there's no expo-specific hosting code that must be
exported.
- This PR adds the ability to host the app with an express server,
different production adapters to follow.

# Test Plan

In addition to all the E2E Metro tests, I've added a new E2E runner
which starts a server and pings different requests to ensure expected
behavior. These run in the CLI as opposed to the `@expo/server` package.

- resolve ENG-10057 ENG-8243 ENG-8082 ENG-8079 ENG-8242 ENG-8081
ENG-8080 ENG-9625

---------

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

show more ...

Move `process.env` polyfill strip to `expo/metro-config`. (#24455)

# Why

Improves the sourcemaps as we aren't modifying the string after the maps
are generated.

---------

Co-authored-by: E

Move `process.env` polyfill strip to `expo/metro-config`. (#24455)

# Why

Improves the sourcemaps as we aren't modifying the string after the maps
are generated.

---------

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

show more ...

Support mocking Node.js externals for client-side bundles. (#24453)

# Why

- Fix regression in https://github.com/expo/expo/pull/24199 which breaks
all Metro web tests.

---------

Co-authore

Support mocking Node.js externals for client-side bundles. (#24453)

# Why

- Fix regression in https://github.com/expo/expo/pull/24199 which breaks
all Metro web tests.

---------

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

show more ...

feat(cli, router, metro, asset): add basePath support (#23911)

# Why

- Add the ability to export websites for hosting from a custom path.
This is required for GitHub pages.
- Resolve ENG-9193

feat(cli, router, metro, asset): add basePath support (#23911)

# Why

- Add the ability to export websites for hosting from a custom path.
This is required for GitHub pages.
- Resolve ENG-9193
- Resolve https://github.com/expo/expo/issues/20562
- Resolve https://github.com/expo/router/issues/165

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

# How

- Add `expo.experiments.basePath` which can be used during `npx expo
export` to modify how assets are referenced.
- Set the `publicPath` in Metro to output as expected.
- Add custom asset writing for web to support stripping the unused
prefix.

- It's unclear if this should also apply to native, and if we should
have platform-specific variations.
- Update Expo Router to support automatically adjusting paths to support
basePath in production builds.
<!--
How did you build this feature or fix this bug and why?
-->

# Test Plan

- [ ] New `expo export` test.

<!--
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]>
Co-authored-by: Aman Mittal <[email protected]>

show more ...

refactor e2e tests (#24385)

# Why

- Split out of https://github.com/expo/expo/pull/23911
- This PR also adds server tests for static rendering.
- Make it easier to run and test e2e metro code.

refactor e2e tests (#24385)

# Why

- Split out of https://github.com/expo/expo/pull/23911
- This PR also adds server tests for static rendering.
- Make it easier to run and test e2e metro code.
<!--
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 ...

[expo-updates] Add fingerprintExperimental runtime version policy (#24126)

# Why

Manually handling runtimeVersions is a big pain for projects that uses
native modules. This PR adds a new runtime

[expo-updates] Add fingerprintExperimental runtime version policy (#24126)

# Why

Manually handling runtimeVersions is a big pain for projects that uses
native modules. This PR adds a new runtime policy that handles this
automatically.

See:

https://discord.com/channels/695411232856997968/1142023605908156476/1142023605908156476

# How

Using
[expo-fingerprint](https://github.com/expo/expo/tree/main/packages/@expo/fingerprint#readme)
to auto-generate a hash for the project.

# Test Plan

I made the changes locally on a working project and the build was
successfully with expo prebuild. I checked the native files and the
runtime version was set to the project hash.

# Checklist

- [x] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [x] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [x] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

Co-authored-by: Expo Bot <[email protected]>
Co-authored-by: Aman Mittal <[email protected]>
Co-authored-by: Kudo Chien <[email protected]>
Co-authored-by: Douglas Lowder <[email protected]>

show more ...

Add support for bun as a package manager. (#24344)

# Why

- Follow up for https://github.com/expo/expo/pull/24168 adding support
for install, prebuild, etc. to use bun as well.

---------

Co

Add support for bun as a package manager. (#24344)

# Why

- Follow up for https://github.com/expo/expo/pull/24168 adding support
for install, prebuild, etc. to use bun as well.

---------

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

show more ...

feat(cli): ensure port is running after build. (#24315)

# Why

If a user runs either build command (`npx expo run:ios` or `npx expo
run:android`) simultaneously, then there is chance for a port c

feat(cli): ensure port is running after build. (#24315)

# Why

If a user runs either build command (`npx expo run:ios` or `npx expo
run:android`) simultaneously, then there is chance for a port conflict.
This change proposes we run a secondary port check after the build to
provide a slightly better user experience. If the port is taken by the
same app, the dev server will be skipped and the process will proceed in
headless-mode, if the port is taken by a different process, then an
error will be thrown.

---------

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

show more ...

chore(cli): delete @expo/dev-server (#24272)

# Why

- I tried this before but the logs endpoint was blocking it.
- I forked the dev server when I wrote the original `expo/cli`, been
meaning to d

chore(cli): delete @expo/dev-server (#24272)

# Why

- I tried this before but the logs endpoint was blocking it.
- I forked the dev server when I wrote the original `expo/cli`, been
meaning to delete the original for a while. The duplicate code and
indirection is making the new server features harder to implement.

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

# How

- Copy/paste remaining code from `@expo/dev-server` in to `@expo/cli`.
- Delete `@expo/dev-server`.
- Drop unused `/logs` and json parser middleware.
- Drop logging mocks.
- Drop experimental Webpack native support.
- Drop legacy react-native middleware support (no longer needed since
everything is versioned).

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

# Test Plan

- Tests should keep passing.
- Need to do some actual runs since there aren't any e2e tests for
various parts of dev-server.

<!--
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] Extend android package name validation (#24155)

[cli] Misleading build message (#24153)

feat(metro, cli, router): production static web source maps support (#24213)

# Why

- Add support for exporting (or skipping) optimally formatted source
maps on web with static rendering enabled.

feat(metro, cli, router): production static web source maps support (#24213)

# Why

- Add support for exporting (or skipping) optimally formatted source
maps on web with static rendering enabled.
- Improved version of https://github.com/expo/expo/pull/22334

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

# How

- Pass a new setting to the custom serializer when exporting for usage
outside of the dev server. This setting will ensure a source map is
created with paths relative to the server root.
- The resources will be adjusted after exporting to reflect the hashed
js filename location.
- When no sourcemap exporting is enabled, the references will be
stripped to prevent getting a chrome warning.


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

# Test Plan

- I added an e2e bundling test for both exporting with and without
sourcemaps.

<!--
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): fix webpack dev server reload socket command. (#24208)

# Why

- fix https://github.com/expo/expo/issues/21994

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

fix(cli): fix webpack dev server reload socket command. (#24208)

# Why

- fix https://github.com/expo/expo/issues/21994

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

Bump minimum required Xcode version. (#24205)

# Why

- https://developer.apple.com/news/upcoming-requirements/?id=04252023a
- This is a breaking change for users as some might need to update
Xco

Bump minimum required Xcode version. (#24205)

# Why

- https://developer.apple.com/news/upcoming-requirements/?id=04252023a
- This is a breaking change for users as some might need to update
Xcode, which is never fun.

---------

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

show more ...

feat(cli): validate android package name (#24194)

# Why

- resolve https://github.com/expo/expo/issues/22428

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

feat(cli): validate android package name (#24194)

# Why

- resolve https://github.com/expo/expo/issues/22428

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

# How

- Added a list of reserved java keywords from wikipedia.
- Tested each category against a gradle build.
- Added additional info to the validation prompt so users have a hint as
to what is incorrect.

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

# Test Plan

- Added unit tests, ran locally

<img width="491" alt="Screenshot 2023-08-30 at 3 23 02 PM"
src="https://github.com/expo/expo/assets/9664363/e5d42702-3818-48f4-ad23-f9f6e821223f">

show more ...

cli(fix): prevent `expo config --json` from logging env var logs (#24192)

# Why

- fix #23325

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts

cli(fix): prevent `expo config --json` from logging env var logs (#24192)

# Why

- fix #23325

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

# How

- Mock the logs before and after the config evaluation.

# Test Plan

- Updated E2E tests to include an env var file and value.

---------

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

show more ...

feat(cli): improve xcode setup instructions (#24191)

# Why

- resolve https://github.com/expo/expo/issues/21727
- This does introduce the slightly breaking change where you need Xcode
10 install

feat(cli): improve xcode setup instructions (#24191)

# Why

- resolve https://github.com/expo/expo/issues/21727
- This does introduce the slightly breaking change where you need Xcode
10 installed. Most users are probably on 12-14.

show more ...

fix!(cli): Favor remote versions endpoint over bundled versions (#24162)

# Why

- We have a versions endpoint with minimal libraries in it, we should
favor it over the bundled versions so we can

fix!(cli): Favor remote versions endpoint over bundled versions (#24162)

# Why

- We have a versions endpoint with minimal libraries in it, we should
favor it over the bundled versions so we can push emergency bumps that
users can access without having to update `expo`.

---------

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

show more ...