<?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-readme</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>748ab554 - [module-scripts] Fix expo-module prepare error from temp kotlin file (#17023)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-module-scripts/bin/expo-module-readme#748ab554</link>
        <description>[module-scripts] Fix expo-module prepare error from temp kotlin file (#17023)# Whyyarn prepare in expo-updates with the following error:```yarn run v1.22.11$ expo-module prepareConfiguring module/Users/kudo/expo/expo/packages/expo-module-scripts/bin/expo-module-readme:115            .replace(/\//g, &apos;.&apos;)            ^TypeError: Cannot read property &apos;replace&apos; of undefined```the error happens if you did ever build expo-updates android code locally and there are kotlin generated files in `android/build`, e.g. `android/build/tmp/kapt3/stubs/debug/expo/modules/updates/UpdatesPackage.java`# Howupdate the `expo-module-readme` matching directory from `android/src/**` and also support `*.kt` files# Test Plan```# generated kotlin temp files$ cd android &amp;&amp; ./gradlew :expo-updates:testDebugUnitTest$ cd ../packages/expo-updates &amp;&amp; yarn prepare```

            List of files:
            /expo/packages/expo-module-scripts/bin/expo-module-readme</description>
        <pubDate>Thu, 14 Apr 2022 02:10:40 +0000</pubDate>
        <dc:creator>Kudo Chien &lt;kudo@expo.dev&gt;</dc:creator>
    </item>
<item>
        <title>b52e368f - Change several expo.io references to expo.dev or exp.host (#16803)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-module-scripts/bin/expo-module-readme#b52e368f</link>
        <description>Change several expo.io references to expo.dev or exp.host (#16803)Docs:- Replaced docs.expo.io links in READMEs with docs.expo.dev- Updated references to docs.expo.io throughout docblocks in source code- Updated package.json files that linked to docs.expo.ioEmails:- Changed some support and test emails to use `@expo.dev`Classic update hosts:- Changed `exp://expo.io` links to `exp://exp.host` links. This change is consistent with the URLs that Expo CLI generates.

            List of files:
            /expo/packages/expo-module-scripts/bin/expo-module-readme</description>
        <pubDate>Wed, 30 Mar 2022 23:53:08 +0000</pubDate>
        <dc:creator>James Ide &lt;ide@users.noreply.github.com&gt;</dc:creator>
    </item>
<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-readme#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-readme</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>9ebb16cf - [expo-module-scripts] Support top-level podspec (#7338)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-module-scripts/bin/expo-module-readme#9ebb16cf</link>
        <description>[expo-module-scripts] Support top-level podspec (#7338)# WhyFrom what I can tell React Native ecosystem leans towards putting podspec at the top level of the package &#8212; let&apos;s support it then!# HowWhen searching for `.podspec` in a library let&apos;s take the whole library into account, not only the `ios` directory.# Test PlanI tested the change when creating `expo-image` (https://github.com/expo/expo/pull/7327).

            List of files:
            /expo/packages/expo-module-scripts/bin/expo-module-readme</description>
        <pubDate>Wed, 11 Mar 2020 15:23:19 +0000</pubDate>
        <dc:creator>Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>0623af9e - Fix workspace linking so that all packages are linked</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-module-scripts/bin/expo-module-readme#0623af9e</link>
        <description>Fix workspace linking so that all packages are linked- Updated the dependencies in the expo package to include the semver versions of the packages in this repo so that Yarn will link them- Forced standalone-ncl to use the core unimodule packages in this repoAlso:- Updated expo-module-readme to print out the name of the package for which we are generating the readme- Made `yarn prepare` in the workspace root just generate the lazy entry point for the expo package instead of running `prepare` in it, which removes some warnings.Tested by opening Expo home locally and verifying that we don&apos;t get an error about vector-icons missing from the module map.

            List of files:
            /expo/packages/expo-module-scripts/bin/expo-module-readme</description>
        <pubDate>Tue, 07 May 2019 20:47:14 +0000</pubDate>
        <dc:creator>James Ide &lt;ide@expo.io&gt;</dc:creator>
    </item>
<item>
        <title>8d441c7e - [packages] Move unimodules foundation to `org.unimodules` scope</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-module-scripts/bin/expo-module-readme#8d441c7e</link>
        <description>[packages] Move unimodules foundation to `org.unimodules` scope

            List of files:
            /expo/packages/expo-module-scripts/bin/expo-module-readme</description>
        <pubDate>Thu, 14 Mar 2019 12:11:47 +0000</pubDate>
        <dc:creator>Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>8864b1cd - Updating READMEs and docs for unimodules and other related changes (#3558)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-module-scripts/bin/expo-module-readme#8864b1cd</link>
        <description>Updating READMEs and docs for unimodules and other related changes (#3558)* Project lifecycle changes and some other cleanup* A bunch of incremental improvements* Make section groups and have them be collapsable* Group API reference too* Shuffle docs a bit for grouping* Tweak styles* Reorder a few things in fundamentals and fix AppAuth name* Create a bare workflow group* Add consistent sections for installation and api to sdk* Remove expo-core from dependencies* Add expo-module script for generating README* Add some helpful links to footer* Update website in unimodules to point to docs* Update READMEs* Backport docs changes and a few small changes* Backport more docs from unversioned* Fix broken links* Fix some more links* Move peerDependencies on unimodule packages to unimodulesPeerDependenciesAlso move some direct dependencies on unimodule packages tounimodulesPeerDependencies. This field is currently unused, butpeerDependencies does not work with transitive dependencies so userswill get a lot of warnings and they won&apos;t be particularly helpful. Versionchanged to * for now because it&apos;s unused and I&apos;m not sure everything isup to date anyhow.* Add note about scoping in expo-font* Update unimodule packages to 3.0* Add Hello World doc

            List of files:
            /expo/packages/expo-module-scripts/bin/expo-module-readme</description>
        <pubDate>Wed, 27 Feb 2019 22:47:39 +0000</pubDate>
        <dc:creator>Brent Vatne &lt;brentvatne@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
