Support pluggable device info providers instead of forcing expo-device #51
Closed
chanphiromsok
started this conversation in
Ideas
Replies: 2 comments 1 reply
|
Sorry for a late response, we've been mostly tracking discussions on discord and gh issues up until this point, so we simply didn't notice it. Regarding the question – we've decided to migrate to expo-device, because we didn't want to enforce a prebuild step. We think we could make it conditionally use one package, or another. We will try to include this change in the next release |
1 reply
|
@chanphiromsok it's been released in the most recent version. Please let us know if everything is correct on your side. Thank you for reporting it! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I recently upgraded Detour to the latest version, and it now requires installing expo-device (#42) as a peer dependency. My app is already using react-native-device-info, so I was wondering if we could have the option to choose between these two libraries. This would help reduce the overall app size a bit.
All reactions