<?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 expo-module-test</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>a9e9eb76 - [ems] Tidy up README and bash directory checks</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-module-scripts/bin/expo-module-test#a9e9eb76</link>
        <description>[ems] Tidy up README and bash directory checks- Remove stray `=` from readme- Remove unnecessary `$(pwd)` from bash scripts- Fix up order of eslint args (options, then dir path at the end). Tested by running `yarn lint` in expo-facebook.- Made podspec glob look for &lt;pkg&gt;/*.podspec and &lt;pkg&gt;/ios/**/*.podspec instead of searching everywhere in the package (specifically we don&apos;t want to descend into node_modules). Tested by running `yarn expo-module readme` in both expo-facebook and expo-image to test both cases.

            List of files:
            /expo/packages/expo-module-scripts/bin/expo-module-test</description>
        <pubDate>Fri, 19 Feb 2021 05:03:41 +0000</pubDate>
        <dc:creator>James Ide &lt;ide@expo.io&gt;</dc:creator>
    </item>
<item>
        <title>ec4c554e - [EMS] Create dev tooling for config plugins (#11574)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-module-scripts/bin/expo-module-test#ec4c554e</link>
        <description>[EMS] Create dev tooling for config plugins (#11574)* plugin for stripe* add plugin clean, build, and lint scripts* Update index.ts* remove template* update naming* Update README.md* Update CHANGELOG.md* added plugin support to et* Update app.json* added testing options* Update checkPackageAsync.ts* added payments to NCL* updated stripe plugin to support iap* Update PaymentsScreen.tsx* Update PaymentsScreen.tsx* Update PaymentsScreen.tsx* Updated docs* Apply suggestions from code reviewCo-authored-by: James Ide &lt;ide@users.noreply.github.com&gt;Co-authored-by: Brent Vatne &lt;brentvatne@gmail.com&gt;* updated types* Update jest-preset-plugin.js* downgrade node* Apply suggestions from code reviewCo-authored-by: James Ide &lt;ide@users.noreply.github.com&gt;* update syntax* ignore plugin builds* unignore* Update packages/expo-module-scripts/README.mdCo-authored-by: James Ide &lt;ide@users.noreply.github.com&gt;Co-authored-by: James Ide &lt;ide@users.noreply.github.com&gt;Co-authored-by: Brent Vatne &lt;brentvatne@gmail.com&gt;

            List of files:
            /expo/packages/expo-module-scripts/bin/expo-module-test</description>
        <pubDate>Thu, 14 Jan 2021 02:02:55 +0000</pubDate>
        <dc:creator>Evan Bacon &lt;baconbrix@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>3a15479d - [build] Add &quot;expo-module-scripts&quot; package for common scripts</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-module-scripts/bin/expo-module-test#3a15479d</link>
        <description>[build] Add &quot;expo-module-scripts&quot; package for common scriptsAll Expo module packages and the Expo SDK package need common scripts, like running TypeScript, unit tests, compiling the TS before publishing, and so on. This introduces a package called &quot;expo-module-scripts&quot; that defines a script called `expo-module` with many commands like `test` and `build`. This helps us use consistent commands with consistent dependency versions (e.g. the same version of TypeScript, Jest, etc...) across all modules so that the Expo SDK is unified.There are commands for common tasks like `build`, `test`, and `clean`. There are also commands for npm lifecycles like `prepare` and `prepublishOnly`. And there are pass-through commands for common development dependencies like `tsc` and `jest`.The module is invokable through the `expo-module` program: `expo-module test` for instance. In a module&apos;s package.json, define a script named &quot;expo-module&quot; that just runs &quot;expo-module&quot; -- this lets us run `yarn expo-module test|build|clean|...`. Also define lifecycle scripts: `&quot;prepare&quot;: &quot;expo-module prepare&quot;` for example. And lastly, define tasks for some common commands for convenience: `&quot;test&quot;: &quot;expo-module test&quot;`.The commands like building and testing run in watch mode since they are meant to be run by humans.Test plan: used this in the Expo SDK module and verified that CI passes.

            List of files:
            /expo/packages/expo-module-scripts/bin/expo-module-test</description>
        <pubDate>Sat, 20 Oct 2018 05:11:21 +0000</pubDate>
        <dc:creator>James Ide &lt;ide@expo.io&gt;</dc:creator>
    </item>
</channel>
</rss>
