| #
47f2bcdc |
| 25-Aug-2023 |
Douglas Lowder <[email protected]> |
[expo-updates] Remove @expo/use-updates (#24113)
# Why
This module is being replaced by the new `useUpdates()` JS API in
`expo-updates` for SDK 50.
# How
Remove the module and all referenc
[expo-updates] Remove @expo/use-updates (#24113)
# Why
This module is being replaced by the new `useUpdates()` JS API in
`expo-updates` for SDK 50.
# How
Remove the module and all references to it.
# Checklist
<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->
- [x] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [x] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [x] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
show more ...
|
| #
e501a7c6 |
| 03-Jul-2023 |
Gabriel Donadel Dall'Agnol <[email protected]> |
[workspace] Bump TypeScript version to 5.1.3 (#23143)
# Why
Closes ENG-9088
# How
Bump TypeScript to the latest, and rebuild all required SDK packages
Had to update `typeRoots` inside `
[workspace] Bump TypeScript version to 5.1.3 (#23143)
# Why
Closes ENG-9088
# How
Bump TypeScript to the latest, and rebuild all required SDK packages
Had to update `typeRoots` inside `expo-module-scripts` due to a change
in TypeScript 5.1 where it no longer walks up automatically looking in
parent directories ([Release
notes](https://devblogs.microsoft.com/typescript/announcing-typescript-5-1-rc/#typeroots-are-consulted-in-module-resolution))
# Test Plan
Ensure that `et cp -a` yields no errors, docs and tools build correctly,
and that CI is green
# Checklist
<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->
- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
show more ...
|
| #
df150c8f |
| 22-Jun-2023 |
Douglas Lowder <[email protected]> |
[expo-updates] Updates state machine for iOS and Android, E2E tests (#22845)
# Why
Implement state machine on Android and iOS.
# How
- New state machine classes on Android and iOS
- Integr
[expo-updates] Updates state machine for iOS and Android, E2E tests (#22845)
# Why
Implement state machine on Android and iOS.
# How
- New state machine classes on Android and iOS
- Integration with UpdatesController/AppController
- State machine change events sent to JS
- Test hook in `@expo/use-updates` to allow E2E tests
- E2E tests for both platforms
# Test Plan
- Manual testing on both platforms
- Unit tests for state machine on both platforms
- New E2E tests for state machine feature
- Existing E2E tests and existing `expo-updates` functionality should be
unaffected
# Checklist
<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->
- [x] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [x] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [x] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
show more ...
|