History log of /expo/packages/expo-file-system/src/ExponentFileSystem.ts (Results 1 – 7 of 7)
Revision Date Author Comments
# 51e273e0 14-Sep-2023 Tomasz Sapeta <[email protected]>

[file-system][iOS] Migrate to Expo Modules API (#23943)


# 6b7802ba 22-Nov-2022 Bartosz Kaszubowski <[email protected]>

[file-system][docs] migrate package to autogenerated docs, APISection tweaks (#20103)


# 8285c032 13-Aug-2021 Tomasz Sapeta <[email protected]>

Rename unimodules imports to expo-modules-core


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

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


# 7e929553 23-Feb-2019 Evan Bacon <[email protected]>

Added types to the ExponentFileSystem platform module (#3560)

* Renamed FS -> ExponentFileSystem
* Fixed bug where constants were being redefined
* Added stricter types to the ExponentFileSystem n

Added types to the ExponentFileSystem platform module (#3560)

* Renamed FS -> ExponentFileSystem
* Fixed bug where constants were being redefined
* Added stricter types to the ExponentFileSystem native module
* Added an empty shim for ExponentFileSystem to be used in standalone and on web

show more ...


# 86804828 21-Feb-2019 Stanisław Chmiela <[email protected]>

[ncl] Standalone, vanilla React Native NCL (#3450)

# Why

Fixes https://github.com/expo/expo/issues/3031. Given our recent effort to move all Expo APIs to universal modules, we would also like to

[ncl] Standalone, vanilla React Native NCL (#3450)

# Why

Fixes https://github.com/expo/expo/issues/3031. Given our recent effort to move all Expo APIs to universal modules, we would also like to be able to easily test them from inside of `expo` monorepo. This pull request adds a “bare”, “vanilla” React Native application in `apps/standalone-ncl` that (on JS side) actually just imports and registers our regular `native-component-list` as the entrypoint.

# How

Created a vanilla RN app, configured to work inside the monorepo, linked and setup `react-native-{screens, gesture-handler, reanimated}` and `expo-{core, react-native-adapter}`. For NCL to work properly, I added the following modules aliases: `~expo -> expo` and `expo -> ./expoResolver`. This will let us mimic `expo` package behavior in NCL without losing the ability to test `expo` in Expo NCL. We will mock/export modules one by one when integrating universal modules into vanilla NCL.

I willingly didn't integrate any universal modules into the app to allow adding-testing-fixing modules to this app one-by-one.

# Test plan

- `yarn start` in `apps/standalone-ncl`
- `pod install` in `apps/standalone-ncl/ios` (I didn't commit `Pods`, but committed `Podfile`)
- run native Xcode project
- run native Android Studio project

<img width="300" alt="obrazek png 2" src="https://user-images.githubusercontent.com/1151041/52430957-85bc8200-2b07-11e9-9ea0-b598b3da7dc3.png">

<img width="300" alt="" src="https://user-images.githubusercontent.com/1151041/52430974-8bb26300-2b07-11e9-8f9f-ca4ff35ac009.png">

show more ...


# 2307aace 31-Jan-2019 Evan Bacon <[email protected]>

[TypeScript] FileSystem migration (#3340)

* Added TS

* Updated testing

* Update FileSystem-test.ts

* Updated `encoding` type

* Updated FileSystem import for `Asset` tests

* Updated sy

[TypeScript] FileSystem migration (#3340)

* Added TS

* Updated testing

* Update FileSystem-test.ts

* Updated `encoding` type

* Updated FileSystem import for `Asset` tests

* Updated syntax

* Update FileSystem-test.ts

* Refined types

* Refined tests

* Update Expo.ts

show more ...