<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in withMetroResolvers.test.ts</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>6fb512fa - fix(cli): Set `preferNativePlatform` to `false` for all web requests. (#23527)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/@expo/cli/src/start/server/metro/__tests__/withMetroResolvers.test.ts#6fb512fa</link>
        <description>fix(cli): Set `preferNativePlatform` to `false` for all web requests. (#23527)# Why- Currently we fallback on the default or user-defined resolver if theexpo resolver fails. Now we&apos;ll skip the default if the expo resolverasserts.- If the user-defined resolver is called, it will now have`preferNativePlatform` disabled. This ensures we never attempt toresolve a web file with `.native` extensions.# Test Plan- Unit tests---------Co-authored-by: Expo Bot &lt;34669131+expo-bot@users.noreply.github.com&gt;

            List of files:
            /expo/packages/@expo/cli/src/start/server/metro/__tests__/withMetroResolvers.test.ts</description>
        <pubDate>Fri, 14 Jul 2023 20:26:58 +0000</pubDate>
        <dc:creator>Evan Bacon &lt;bacon@expo.io&gt;</dc:creator>
    </item>
<item>
        <title>c0a96678 - Upgrade react-native 0.72.0-rc.5 (#22588)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/@expo/cli/src/start/server/metro/__tests__/withMetroResolvers.test.ts#c0a96678</link>
        <description>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 -&gt; 0.72.0-rc.5`  - `metro-react-native-babel-preset 0.73.9 -&gt; 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&amp;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&apos;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&apos;s still react-native-web@~0.18.10.- currently disable ci typecheck for @expo/cli because of upstream metro typescript support. i&apos;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&apos;s related to the react scheduler change. i&apos;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&apos;t do this in this upgrade.# Test Plan- &#9989; fabric-tester (without expo-dev-client)- &#9989; 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.- &#9989; bare-expo- &#9989; unversioned expo go + ncl---------Co-authored-by: Tomasz Sapeta &lt;tomasz.sapeta@swmansion.com&gt;

            List of files:
            /expo/packages/@expo/cli/src/start/server/metro/__tests__/withMetroResolvers.test.ts</description>
        <pubDate>Wed, 07 Jun 2023 07:37:48 +0000</pubDate>
        <dc:creator>Kudo Chien &lt;kudo@expo.dev&gt;</dc:creator>
    </item>
<item>
        <title>837127ed - fix(cli): allow chained Metro resolvers to resolve when the predecessor resolvers throw a Metro resolution error. (#20704)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/@expo/cli/src/start/server/metro/__tests__/withMetroResolvers.test.ts#837127ed</link>
        <description>fix(cli): allow chained Metro resolvers to resolve when the predecessor resolvers throw a Metro resolution error. (#20704)# WhyReimplements #19874 but with tests and proper checking.&lt;!--Please describe the motivation for this PR, and link to relevant GitHubissues, forums posts, or feature requests.--&gt;# How- When a metro resolver throws a metro resolution error, we shouldattempt to resolve using the next resolver in the chain.- Added debug logs so users can examine the progress.- Added tests for all known cases.Co-authored-by: Expo Bot &lt;34669131+expo-bot@users.noreply.github.com&gt;

            List of files:
            /expo/packages/@expo/cli/src/start/server/metro/__tests__/withMetroResolvers.test.ts</description>
        <pubDate>Wed, 04 Jan 2023 16:26:21 +0000</pubDate>
        <dc:creator>Evan Bacon &lt;bacon@expo.io&gt;</dc:creator>
    </item>
</channel>
</rss>
