Name of library: expo-location
Details
-
Number of stars in GH: 44.4k
-
Number of monthly downloads: 395k weekly downloads
-
Number of releases in the last year: 24
-
Level of activity in the repo: High
-
Alternatives:
-
Are security concerns brought up and addressed in the library's repo? No security concerns
-
How many dependencies does this lib use that will be brought into our code? 0
-
What will the effect be on the bundle size of our code? expo-location has 573 kB of unpacked size. If we were to replace our current geolocation library with it (which has 168 kB of unpacked size + 22.2 kB of unpacked size of react-native-android-location-enabler which can also be replaced by expo-location) then there will be 382.8 kB more of unpacked size after the migration to expo-location. On the plus side, it has richer API in case we will want to add more location-related features in the future.
The migration from @react-native-community/geolocation to expo-location doesn't look hard as it's only used in getCurrentLocation which has only 7 references in the codebase.
Issue Owner
Current Issue Owner: @
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022003938138994591872
- Upwork Job ID: 2003938138994591872
- Last Price Increase: 2025-12-24
Name of library:
expo-locationDetails
Link to package: https://www.npmjs.com/package/expo-location https://docs.expo.dev/versions/latest/sdk/location/
Problem solved by using this package:
Number of stars in GH: 44.4k
Number of monthly downloads: 395k weekly downloads
Number of releases in the last year: 24
Level of activity in the repo: High
Alternatives:
@react-native-community/geolocationthat we're already using, but it has 2x less weekly downloads, there was no release for over a year, and there is no support for background location updates on Android (related issue)Are security concerns brought up and addressed in the library's repo? No security concerns
How many dependencies does this lib use that will be brought into our code? 0
What will the effect be on the bundle size of our code?
expo-locationhas 573 kB of unpacked size. If we were to replace our current geolocation library with it (which has 168 kB of unpacked size + 22.2 kB of unpacked size of react-native-android-location-enabler which can also be replaced byexpo-location) then there will be 382.8 kB more of unpacked size after the migration toexpo-location. On the plus side, it has richer API in case we will want to add more location-related features in the future.The migration from
@react-native-community/geolocationtoexpo-locationdoesn't look hard as it's only used ingetCurrentLocationwhich has only 7 references in the codebase.Issue Owner
Current Issue Owner: @Upwork Automation - Do Not Edit