<?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 expotools</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>2fd75d6d - Deprecate source-login-scripts.sh (#18330)</title>
        <link>http://172.16.0.5:8080/history/expo/bin/expotools#2fd75d6d</link>
        <description>Deprecate source-login-scripts.sh (#18330)# Whythe `source-login-scripts.sh` introduced a lot of pain where the community reported much build errors from it. it doesn&apos;t support shells other than zsh and bash. this pr find a new way to deal with xcode building issues that it cannot find the correct nodejs path.close ENG-4864close ENG-5242# Howreact-native introduces `.xcode.env` and `.xcode.env.local` for developers to override the `$NODE_BINARY`: https://github.com/facebook/react-native/pull/33546to make sure building success from expo-constants, expo-updates, and also the app target when generating bundles. i would like to reuse the `.xcode.env` and `.xcode.env.local` from react-native. this pr further generates `.xcode.env.local` automatically for the app during `pod install`. we can ensure that `pod install` is executed from shell and nodejs is available. so we will generate `export NODE_BINARY=&quot;$(command -v node)&quot;` in the `.xcode.env.local`. for xcode, the path will be `$PODS_ROOT/../.xcode.env.local`, every xcode subprojects can source the file to get correct `$NODE_BINARY`.# Test Plan- building bare-expo from xcode (opening xcode by macos finder)- building bare-expo by `yarn ios`- updates e2e ci passed- building expo-go (prerequisite: #18344) Co-authored-by: James Ide &lt;ide@users.noreply.github.com&gt;

            List of files:
            /expo/bin/expotools</description>
        <pubDate>Mon, 25 Jul 2022 12:28:01 +0000</pubDate>
        <dc:creator>Kudo Chien &lt;kudo@expo.dev&gt;</dc:creator>
    </item>
<item>
        <title>eeffdb10 - [tools] Move tools/expotools one folder up (#11410)</title>
        <link>http://172.16.0.5:8080/history/expo/bin/expotools#eeffdb10</link>
        <description>[tools] Move tools/expotools one folder up (#11410)

            List of files:
            /expo/bin/expotools</description>
        <pubDate>Mon, 21 Dec 2020 18:51:31 +0000</pubDate>
        <dc:creator>Tomasz Sapeta &lt;1714764+tsapeta@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>93a12a7d - [expotools] throw nix out of expotools &#55356;&#57225; (#4469)</title>
        <link>http://172.16.0.5:8080/history/expo/bin/expotools#93a12a7d</link>
        <description>[expotools] throw nix out of expotools &#55356;&#57225; (#4469)# WhyPreparing the ground to #4428 As far as I know there is no need to utilize nix packages in expotools, however this was always a pain for us since this takes so much time before we can run any command. To be honest I usually run expotools directly from `tools/expotools/bin/expotools.js` to omit nix.# How- Removed nix from expotools stub - can we open a champagne already? &#55356;&#57214; - Added a wrapper around expotools that ensures build and node_modules folders are up to date- Made asorted improvements in the output of expotools commandsScreenshot:&lt;img width=&quot;1178&quot; alt=&quot;Screenshot 2019-06-07 at 00 22 13&quot; src=&quot;https://user-images.githubusercontent.com/1714764/59070333-abda0f00-88ba-11e9-9d9d-a5fdbbec0315.png&quot;&gt;# Test PlanTried some different commands with different flags to cover all use cases.

            List of files:
            /expo/bin/expotools</description>
        <pubDate>Fri, 07 Jun 2019 08:43:44 +0000</pubDate>
        <dc:creator>Tomasz Sapeta &lt;tsapeta@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>58b9ee98 - Move tools/bin to bin</title>
        <link>http://172.16.0.5:8080/history/expo/bin/expotools#58b9ee98</link>
        <description>Move tools/bin to bin

            List of files:
            /expo/bin/expotools</description>
        <pubDate>Tue, 11 Dec 2018 20:06:21 +0000</pubDate>
        <dc:creator>Nick Novitski &lt;nick@expo.io&gt;</dc:creator>
    </item>
</channel>
</rss>
