History log of /expo/packages/expo-module-scripts/bin/expo-module-readme (Results 1 – 7 of 7)
Revision Date Author Comments
# 748ab554 14-Apr-2022 Kudo Chien <[email protected]>

[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
Config

[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, '.')
^

TypeError: Cannot read property 'replace' 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 && ./gradlew :expo-updates:testDebugUnitTest

$ cd ../packages/expo-updates && yarn prepare
```

show more ...


# b52e368f 30-Mar-2022 James Ide <[email protected]>

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 so

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.

show more ...


# a9e9eb76 19-Feb-2021 James Ide <[email protected]>

[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). Teste

[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 <pkg>/*.podspec and <pkg>/ios/**/*.podspec instead of searching everywhere in the package (specifically we don'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.

show more ...


# 9ebb16cf 11-Mar-2020 Stanisław Chmiela <[email protected]>

[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 — let's support it then!

[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 — let's support it then!

# How

When searching for `.podspec` in a library let'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).

show more ...


# 0623af9e 07-May-2019 James Ide <[email protected]>

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

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 repo

Also:
- 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't get an error about vector-icons missing from the module map.

show more ...


# 8d441c7e 14-Mar-2019 Stanisław Chmiela <[email protected]>

[packages] Move unimodules foundation to `org.unimodules` scope


# 8864b1cd 27-Feb-2019 Brent Vatne <[email protected]>

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 ha

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't be particularly helpful. Version
changed to * for now because it's unused and I'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

show more ...