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

Publish packages

@expo/[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
expo-module-

Publish packages

@expo/[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]

show more ...

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
[email protected]
[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 ...

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
[email protected]

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[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]

show more ...

chore(create-expo): move package from `expo/expo-cli` to `expo/expo` (#24373)

# Why

Moving this actively used/developed package from
[expo/expo-cli](https://github.com/expo/expo-cli) to
[expo/e

chore(create-expo): move package from `expo/expo-cli` to `expo/expo` (#24373)

# Why

Moving this actively used/developed package from
[expo/expo-cli](https://github.com/expo/expo-cli) to
[expo/expo](https://github.com/expo/expo).

> ⚠️ ~~Blocked by `@expo/package-manager` changes being merged only in
`sdk-49` and not `main`. See https://github.com/expo/expo/pull/24376~~
> Merged in this PR!

# How

- Copied project into **packages/create-expo-app**
- Applied various changes to fit it in the repository

# Test Plan

See CI

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

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

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/pac

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[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]
[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]
@expo/[email protected]
[email protected]
[email protected]

show more ...

fix(cli): add missing `minimatch` and `glob` dependencies (#22941)

# Why

Fixes #22884

# How

See PR #22939 for a list of all missing dependencies (including some
"expected missing dependenc

fix(cli): add missing `minimatch` and `glob` dependencies (#22941)

# Why

Fixes #22884

# How

See PR #22939 for a list of all missing dependencies (including some
"expected missing dependencies")

### `minimatch`

**`minimatch` was the original offender from #22884, added
`[email protected]` - notated as `minimatch@^3.0.4`.**

<details><summary>See output of <code>yarn why minimatch</code> - after
fixing the issue</summary>

<img width="895" alt="image"
src="https://github.com/expo/expo/assets/1203991/bc2aaf33-cb31-4150-8890-83404d0a4ef7">

</details>

<details><summary>See most used notations in repo</summary>

<img width="525" alt="image"
src="https://github.com/expo/expo/assets/1203991/b65e899a-9d75-48bb-b156-072c4551d289">

</details>

### `glob`

**`glob` popped up in the list from PR #22939, added `[email protected]` -
notated as `glob@^7.1.7`**

<details><summary>See output of <code>yarn why glob</code> - after
fixing the issue</summary>

<img width="880" alt="image"
src="https://github.com/expo/expo/assets/1203991/07b71ec6-b08e-43ba-8c0a-4581928f2feb">

</details>

<details><summary>See most used notations in repo</summary>

<img width="527" alt="image"
src="https://github.com/expo/expo/assets/1203991/8df1b0d0-e757-4017-8506-6a3a1ed55dde">

</details>

### `memfs`

**`memfs` although used as devDependency, it should also be listed as
devDependency, added `[email protected]` - notated as `memfs@^3.2.0`**

<details><summary>See output of <code>yarn why memfs</code> - after
fixing the issue</summary>

<img width="585" alt="image"
src="https://github.com/expo/expo/assets/1203991/a9ecfdf8-293e-41f7-bb3a-30e79f0afd84">

</details>

<details><summary>See most used notations in repo</summary>

<img width="524" alt="image"
src="https://github.com/expo/expo/assets/1203991/4f6d8e9a-44c9-45ca-88a3-d27e35569f0f">

</details>


# Test Plan

Hard to test, but you must install the package using [isolated
modules](https://github.com/npm/rfcs/blob/main/accepted/0042-isolated-mode.md).
Unfortunately, we don't fully support that yet.

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

show more ...

fix(expo, asset, cli)!: unify asset hashing (#24090)

# Why

Convert the `../` segments of the server URL to `_` to support
monorepos. This same transformation takes place in
`AssetSourceResolver

fix(expo, asset, cli)!: unify asset hashing (#24090)

# Why

Convert the `../` segments of the server URL to `_` to support
monorepos. This same transformation takes place in
`AssetSourceResolver.web` (expo-assets, expo-image) and
`persistMetroAssets` of Expo CLI, this originally came from the [Metro
opinion](https://github.com/react-native-community/cli/blob/2204d357379e2067cebe2791e90388f7e97fc5f5/packages/cli-plugin-metro/src/commands/bundle/getAssetDestPathIOS.ts#L19C5-L19C10).

The purpose is to ensure no URL like `/foo/../bar.png` is requested, as
the result would be `/bar.png` which wouldn't work. The of how to handle
this didn't come from us, but we do need to ensure it's unified. At a
high-level, this does prevent the usage of certain files, as
`/foo/../bar.png` will be `/foo/_bar.png`, meaning a file named
`/foo/_bar.png` cannot also exist. This logic, while applied at runtime,
is actually only valid for production exports as we don't move or alias
files in development. The only way to have valid development files is to
ensure `../` never appears in the URL, i.e. by using
`unstable_serverRoot`.

- Drop legacy `expo/tools/hashAssetFiles.js` in favor of `expo-asset`
version.
- Unify runtime logic of asset file loading for monorepos.
- Split out of https://github.com/expo/expo/pull/23911

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

show more ...

chore: improve expo router testing (#23795)

# Why

- Ensure the various aspects of `npx expo export` continue to work with
the latest Expo Router/Metro depdencies.
- We had a bundling testing fo

chore: improve expo router testing (#23795)

# Why

- Ensure the various aspects of `npx expo export` continue to work with
the latest Expo Router/Metro depdencies.
- We had a bundling testing for Expo Router but it wasn't linked to the
monorepo so the dependencies weren't in sync.

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

# How

- Create a new app in `apps/` which is synchronized with the monorepo.
- This app contains multiple expo-router directories and various dynamic
settings.
- Fold the `expo-router` e2e tests into `@expo/cli`.
- Test static rendering, single-page application exporting, and the
native url polyfill (api).

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

# Test Plan

- The CLI E2E tests should pass.

---------

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

show more ...

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
[email protected]
create-expo-module

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[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]
[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]
@expo/[email protected]
[email protected]

show more ...

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
b

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[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]
@expo/[email protected]
[email protected]

show more ...

feat: add generated types for Expo Router useSegment (#22629)

# Why

* Add type generation for Expo Router's `useSegment`
* Adds code comments and renames a few internal types.
* Refactored the

feat: add generated types for Expo Router useSegment (#22629)

# Why

* Add type generation for Expo Router's `useSegment`
* Adds code comments and renames a few internal types.
* Refactored the `useSearchParams` types
* Add default to `Href<T>`

Note that this is not a breaking change as the generated types are only
present inside the users' cache and should not be committed. Next time
the user starts the dev server they will get the new generated types.

## Questions

@EvanBacon Given the route `/(app)/note/[note]/` does useSegments return
the group?

## `useSearchParams`

This hook was a bit strange as its signature changed when you enabled
types routes.

Without: `useSearchParams<T extends Record<string, string>(): T`
With: `useSearchParams<T extends Route>(): SearchParams<T>`

This PR updates the TypedRoutes version to accept either a `Route` or a
`Record`. This `Record` is still typed checked and it must satisfy a
possible SearchParams object.

For example

```tsx
// This will only work if you have a [test] route somewhere in your app
const { test } = useSearchParams<{ test: string }>()
```

I quite like this as it allows you to cherry-pick the param that you
need.

Note that this obviously doesn't do a runtime check for it maybe be
correct, but its a start.

## Href<T>

Href<T> has a default value and by default now represents all possible
Hrefs. You can use the generic to reduce it down.

---------

Co-authored-by: evanbacon <[email protected]>

show more ...

Publish packages

@expo/[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
expo-dev-l

Publish packages

@expo/[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]

show more ...

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
[email protected]
expo-build-pr

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[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]

show more ...

Upgrade semver and json5 for remove security vulnerabilities (#23113)

# Why
Integrate Expo SDK in a bare flow project, creates new security
vulnerabilities.

![Screenshot 2023-06-26 at 9 52 16

Upgrade semver and json5 for remove security vulnerabilities (#23113)

# Why
Integrate Expo SDK in a bare flow project, creates new security
vulnerabilities.

![Screenshot 2023-06-26 at 9 52 16
AM](https://github.com/expo/expo/assets/10479750/590f3bae-e1e0-4452-9669-3aebb3641e0a)

This PR upgrade the Libs to remove those vulnerabilities


[CVE-2022-46175](https://www.mend.io/vulnerability-database/CVE-2022-46175)

[CVE-2023-0842](https://www.mend.io/vulnerability-database/CVE-2023-0842)
- It's already up to date

[CVE-2022-25883](https://www.mend.io/vulnerability-database/CVE-2022-25883)

[CVE-2022-25883](https://www.mend.io/vulnerability-database/CVE-2022-25883)

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

# How
It's a simple non-break changes lib upgrades
<!--
How did you build this feature or fix this bug and why?
-->

# Test Plan
CI should pass
<!--
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.
-->

- [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: Brent Vatne <[email protected]>

show more ...

Publish packages

@expo/[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Publish packages

@expo/[email protected]
@expo/[email protected]
[email protected]
[email protected]

Publish packages

@expo/[email protected]
@expo/[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
ex

Publish packages

@expo/[email protected]
@expo/[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

show more ...

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

show more ...

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
babel-preset-ex

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[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]
[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]
@expo/[email protected]
[email protected]

show more ...

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
expo-kee

Publish packages

@expo/[email protected]
@expo/[email protected]
@expo/[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]

show more ...

Publish packages

[email protected]
[email protected]
[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/prebuild-co

Publish packages

[email protected]
[email protected]
[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
@expo/[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]

show more ...