<?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 externals.ts</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>8be58d21 - fix(cli): fix externals for Metro Node.js rendering. (#22695)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/@expo/cli/src/start/server/metro/externals.ts#8be58d21</link>
        <description>fix(cli): fix externals for Metro Node.js rendering. (#22695)

            List of files:
            /expo/packages/@expo/cli/src/start/server/metro/externals.ts</description>
        <pubDate>Wed, 31 May 2023 00:02:26 +0000</pubDate>
        <dc:creator>Evan Bacon &lt;bacon@expo.io&gt;</dc:creator>
    </item>
<item>
        <title>57eba0f9 - feat(cli): add node target and externals to Metro (#21886)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/@expo/cli/src/start/server/metro/externals.ts#57eba0f9</link>
        <description>feat(cli): add node target and externals to Metro (#21886)# WhyIn order to bundle for Node.js targets using Metro (required for ReactServer Components and other features), we need to add support forleaving the Node.js imports in-tact (no first-class support), and theability to indicate that we&apos;re targeting Node.js without changing theplatform from web.&lt;!--Please describe the motivation for this PR, and link to relevant GitHubissues, forums posts, or feature requests.--&gt;# How- Use `resolver.environment` and `transform.environment` to partiallyinvalidate the Metro cache and pass custom options to the transformer(usage currently unimplemented) and resolver.- Tap Node.js files in the user project under`.expo/metro/externals/[module]/index.js` and redirect requests to thesemodules when bundling for Node.js environments.- Tap a polyfill which exposes `$$require_external` on the global.`$$require_external` can be used to access the environment require fromanywhere in the bundle.- `$$require_external` asserts when used in the browser or native (whereit shouldn&apos;t be available).&lt;!--How did you build this feature or fix this bug and why?--&gt;# Test Plan- Added unit tests.- Tested against an Expo Router project.&lt;!--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.--&gt;# 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/start/server/metro/externals.ts</description>
        <pubDate>Wed, 29 Mar 2023 22:27:23 +0000</pubDate>
        <dc:creator>Evan Bacon &lt;bacon@expo.io&gt;</dc:creator>
    </item>
</channel>
</rss>
