Page MenuHomePhabricator

[native] Bump expo and expo-image
ClosedPublic

Authored by bartek on May 8 2023, 11:28 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 1, 3:35 PM
Unknown Object (File)
Wed, Oct 30, 2:40 PM
Unknown Object (File)
Tue, Oct 29, 6:08 PM
Unknown Object (File)
Tue, Oct 29, 4:00 AM
Unknown Object (File)
Sun, Oct 27, 6:02 PM
Unknown Object (File)
Sun, Oct 27, 3:47 AM
Unknown Object (File)
Sun, Oct 27, 3:47 AM
Unknown Object (File)
Sun, Oct 27, 3:46 AM
Subscribers

Details

Summary

Resolves ENG-3752. Bumped expo-image to 1.2.0 - version that supports thumbhash. This also required bumping expo package in order to bump its dependency expo-modules-core to 1.1.1.

Test Plan

Built both iOS and Android. Played around - photo messages and avatars are still displayed correctly. Added dummy placeholder={{ thumbhash }} prop to Image component to ensure thumbhash works.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

atul added 1 blocking reviewer(s): ashoat.

Changes look good, adding @ashoat as blocking (as formality) since it's a dependency diff.

native/expo-modules/aes-crypto/package.json
10 ↗(On Diff #26239)

Think we typically prefix dependencies w/ ^.

Is there a reason we should be explicit here about specifying version instead of range?

native/expo-modules/aes-crypto/package.json
10 ↗(On Diff #26239)

I had a strange issue where yarn was resolving this to the wrong version and caused duplicated version in the lockfile.
In case of expo-modules, explicit version is not a big deal as long as it matches the resolved version of the app's dependency (app -> expo -> expo-modules-core).
I can try with range version to see if it resolves correctly

native/expo-modules/aes-crypto/package.json
10 ↗(On Diff #26239)

The ~ operator works as expected...
But, the expo package uses a strict version here: https://github.com/expo/expo/blob/8147ccf57bd0f7135f9ed1503cad695d43f9a702/packages/expo/package.json#L75

This revision is now accepted and ready to land.May 9 2023, 6:21 AM
This revision was automatically updated to reflect the committed changes.