<?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 getMetroDebugProperties-test.ts</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>d42dd5d4 - feature(cli): add experimental metro config telemetry (#20885)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/@expo/cli/src/utils/analytics/__tests__/getMetroDebugProperties-test.ts#d42dd5d4</link>
        <description>feature(cli): add experimental metro config telemetry (#20885)# WhyWe need to have visibility on what experimental features are being used,in order to prioritize supporting or finishing these features.# HowAdded a telemetry event when instantiating Metro, for both `npx expostart` and `npx expo export`.# Test PlanSee added test, if a property isn&apos;t available, it doesn&apos;t matter.# Checklist&lt;!--Please check the appropriate items below if they apply to your diff.This is required for changes to Expo modules.--&gt;- [ ] 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` &amp; EAS Build (eg:updated a module plugin).---------Co-authored-by: Expo Bot &lt;34669131+expo-bot@users.noreply.github.com&gt;

            List of files:
            /expo/packages/@expo/cli/src/utils/analytics/__tests__/getMetroDebugProperties-test.ts</description>
        <pubDate>Thu, 09 Feb 2023 14:06:41 +0000</pubDate>
        <dc:creator>Cedric van Putten &lt;me@bycedric.com&gt;</dc:creator>
    </item>
</channel>
</rss>
