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

Apple TV support 2: add TV template, fix config plugin, add CI (#24411)

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

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

[config-types] Remove classic updates (#24066)

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

chore: update tests with latest fixtures. (#23763)

# Why

- fix tests
- fix template

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

chore: update tests with latest fixtures. (#23763)

# Why

- fix tests
- fix template

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

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

Sync SDK changelogs with sdk-49 branch [skip ci]

refactor(config-plugins): add existing native files ignore option (#23165)

# Why

Part of ENG-8481

This option helps to align the entitlements more to what users would
expect. With this, we ca

refactor(config-plugins): add existing native files ignore option (#23165)

# Why

Part of ENG-8481

This option helps to align the entitlements more to what users would
expect. With this, we can fetch the entitlements without the native
files, if the user has gitignored them.

> Note, this is an opt-in and does not change the default behavior.

# How

- Added opt-in option `ignoreExistingNativeFiles` to `evalModsAsync`

# Todo

In EAS CLI, we already know if the user has ignored certain paths. With
this feature, we can enable this option (with the proper warnings and
opt-out if they need to).

See: https://github.com/expo/eas-cli/pull/1906

# Test Plan

See added tests.

> **Note**
> I created the glob mocks by using the vscode launch config, and added
a breakpoint whenever an "unexpected" glob was used. By doing that
through vscode, I could quickly find all globs that were executed for
this test. See config below if you want to try it too.

<details><summary>vscode launch config</summary>

```json
{
"configurations": [
{
"name": "Test mods",
"request": "launch",
"runtimeArgs": ["jest", "--verbose", "withIosBaseMods"],
"runtimeExecutable": "yarn",
"cwd": "${workspaceFolder}/packages/@expo/config-plugins",
"skipFiles": ["<node_internals>/**"],
"type": "node",
"console": "integratedTerminal",
"internalConsoleOptions": "neverOpen"
}
]
}

```

</details>

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

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

[config-plugins][prebuild-config] remove deprecated package in AndroidManifext.xml (#23056)

# Why

seeing a gradle build warning from a sdk49 project after prebuild:

```
> Task :app:processDeb

[config-plugins][prebuild-config] remove deprecated package in AndroidManifext.xml (#23056)

# Why

seeing a gradle build warning from a sdk49 project after prebuild:

```
> Task :app:processDebugMainManifest
package="com.sdk49" found in source AndroidManifest.xml: /Users/kudo/sdk49/android/app/src/main/AndroidManifest.xml.
Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated.
Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace
This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information.
/Users/kudo/sdk49/android/app/src/debug/AndroidManifest.xml:21:9-30:20 Warning:
provider#expo.modules.filesystem.FileSystemFileProvider@android:authorities was tagged at AndroidManifest.xml:21 to replace other declarations but no other declaration present
```

# How

we have the filled the application id to **build.gradle** `namespace` in the `withPackageGradle` plugin already. this pr just removes the deprecated `withPackageManifest` plugin.

# Test Plan

- ci passed

show more ...

[build-properties] Add useCleartextTraffic option (#23043)

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

[templates][config-plugins][dev-server] aligned hermesEnabled property (#21067)

# Why

react-native 0.71 introduces `hermesEnabled` gradle property which is conflict with the original `expo.jsEngi

[templates][config-plugins][dev-server] aligned hermesEnabled property (#21067)

# Why

react-native 0.71 introduces `hermesEnabled` gradle property which is conflict with the original `expo.jsEngine` in gradle.properties. this pr tries to align the `hermesEnabled` as upstream.
close ENG-7228

# How

deprecate `expo.jsEngine` in **gradle.properties** and use `hermesEnabled` instead.

# Test Plan

ci passed

show more ...

chore(config-plugins, prebuild-config): bump xml2js (#22872)

# Why

Hide NPM warnings

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

chore(config-plugins, prebuild-config): bump xml2js (#22872)

# Why

Hide NPM warnings

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

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

feat(cli,router): support src/app directory in Expo Router (#22748)

# Why

- related https://github.com/expo/router/pull/629

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

feat(cli,router): support src/app directory in Expo Router (#22748)

# Why

- related https://github.com/expo/router/pull/629

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

Upgrade react-native 0.72.0-rc.5 (#22588)

# Why

upgrade react-native 0.72 for sdk 49
close ENG-8011

# How

- bump package versions
- `react-native 0.71.3 -> 0.72.0-rc.5`
- `metro-reac

Upgrade react-native 0.72.0-rc.5 (#22588)

# Why

upgrade react-native 0.72 for sdk 49
close ENG-8011

# How

- bump package versions
- `react-native 0.71.3 -> 0.72.0-rc.5`
- `metro-react-native-babel-preset 0.73.9 -> 0.76.5`
- [bare-expo][templates][fabric-tester] migrate template base on [upgrade-helper](https://react-native-community.github.io/upgrade-helper/?from=0.71.7&to=0.72.0-rc.5)
- [expo-template-tabs] remove the metro version overrides for expo-router.
- [core][dev-laucher][dev-menu][media-library][screen-orientation][splash-screen][updates-interface][updates] add the `install_modules_dependencies` to support new architecture + use_frameworks!
- [core][autolinking] fix some new architecture error on ios
- [react-native-lab] update our fork to 0.72.0-rc.5 based
- [go][tools] fix **react-native-lab/react-native/packages/react-native** path move because of react-native's repo monorepo changes
- [go][android] fix gradle 8 errors
- [go][ios] add `RCT_REMOTE_PROFILE=0` to fix the `RCT_ENABLE_INSPECTOR needs to be set to fulfill RCT_REMOTE_PROFILE` build error
- [ncl] remove `ProgressViewIOS` / `ProgressBarAndroid` since they are deprecated/removed in 0.72
- [dev-menu][dev-launcher] rebuild bundles

# Note

- react-native-web is not bumped because of the [issue](https://github.com/necolas/react-native-web/issues/2523), so it's still react-native-web@~0.18.10.
- currently disable ci typecheck for @expo/cli because of upstream metro typescript support. i'll have another pr to fix those errors.
- updates e2e ci on android is broken at [here](https://github.com/expo/expo/blob/fada3d764957779fbfc3d7b723d185db1d933d95/packages/expo-updates/e2e/fixtures/Updates.e2e.ts#L518). i doubt if that's related to the react scheduler change. i'd disabled the failed test case.
- the react-native upstream [migrated away the `@types/jest`](https://github.com/facebook/react-native/pull/36068). i was afraid that will be a breaking change to the existing jest test code since it requires the explicit `@jest/globals` import. i didn't do this in this upgrade.

# Test Plan

- ✅ fabric-tester (without expo-dev-client)
- ✅ ci passed. there are some errors which are known:
- updates e2e on android: as mentioned above
- ios expo go on eas build: versioned expo go are broken on eas build m1 worker. this is also happening on main.
- android client: no space left on the ubuntu worker. this is also happening on main.
- ✅ bare-expo
- ✅ unversioned expo go + ncl

---------

Co-authored-by: Tomasz Sapeta <[email protected]>

show more ...

Disable minimum frame duration by default (CADisableMinimumFrameDurationOnPhone) (#22751)

# Why

A lot of users would benefit from this functionality but aren't aware of
its existence. This chang

Disable minimum frame duration by default (CADisableMinimumFrameDurationOnPhone) (#22751)

# Why

A lot of users would benefit from this functionality but aren't aware of
its existence. This change will make
`CADisableMinimumFrameDurationOnPhone` be set in the prebuild template
by default.

Users can overwrite the value with the following `app.json`
configuration:

```json
{
"expo": {
"ios": {
"infoPlist": {
"CADisableMinimumFrameDurationOnPhone": false
}
}
}
}
```

- It's unclear if this feature has any negative side-effects.

---------

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

show more ...

[config-plugins] mark target as signable/non-signable (#22454)

# Why

Part of a fix for https://github.com/expo/eas-cli/issues/1812.
A user has a project with a framework target. EAS CLI expects

[config-plugins] mark target as signable/non-signable (#22454)

# Why

Part of a fix for https://github.com/expo/eas-cli/issues/1812.
A user has a project with a framework target. EAS CLI expects him to set
up credentials for that target.

# How

- `findApplicationTargetWithDependenciesAsync` is used in EAS CLI to
find targets for which we need to set up credentials.
- Framework targets are not signable. Mark them as non-signable.

# Test Plan

Added test case.

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]

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

show more ...

feat(config plugins): better support out of tree support (#22209)

# Why

Fix various validation issues when using `nexpo prebuild --platform
windows --template
https://github.com/microsoft/react

feat(config plugins): better support out of tree support (#22209)

# Why

Fix various validation issues when using `nexpo prebuild --platform
windows --template
https://github.com/microsoft/react-native-windows-samples/tree/main/samples/AppServiceDemo`

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

---------

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

show more ...