App: [HOLD for payment 2024-03-26] [$500] [New architecture] Replace `@oguzhnatly/react-native-image-manipulator` with `expo-image-manipulator`
Name of library: expo-image-manipulator
More context: https://expensify.slack.com/archives/C01GTK53T8Q/p1707293299589539 Discussion here: https://expensify.slack.com/archives/C01GTK53T8Q/p1707293319626329
Details
- Link to package: https://www.npmjs.com/package/expo-image-manipulator
- Problem solved by using this package: The library we’re using now (
@oguzhnatly/react-native-image-manipulator) is a transitive fork ofexpo-image-manipulator. The original package is more actively maintained and usesexpo-modules-coreso it should support both, the new and the old architecture. - Number of stars in GH: 26.7k
- Number of monthly downloads: 42,954
- Number of releases in the last year: 9
- Level of activity in the repo: high
- Alternatives: @oguzhnatly/react-native-image-manipulator or any of the other expo-free forks of this library.
- Are security concerns brought up and addressed in the library’s repo?
- How many dependencies does this lib use that will be brought into our code?
0 – since we already have the Expo modules core.
- What will the effect be on the bundle size of our code?
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~01f064b153d795f898
- Upwork Job ID: 1766142757478912000
- Last Price Increase: 2024-03-08
About this issue
- Original URL
- State: closed
- Created 5 months ago
- Reactions: 5
- Comments: 31 (15 by maintainers)
Payment Summary:
Contributor: @kowczarz no payment, agency contributor C+ Review: @mananjadhav $500 please request in newdot
@hungvu193 pls apply for payment in upwork - https://www.upwork.com/jobs/~0155bf7bf36c1319ef
I will do this tomorrow
this was reverted so reopening
We have got I believe 6 or 7 👍 from App deployers across GH and Slack and 0 pushback so we can go ahead with the PR @kowczarz
I traced back the reason for using this fork to help determine my decisions and found it here: https://github.com/Expensify/App/issues/6301#issuecomment-1100758657
Not having expo at the time was the main reason for using the fork, and because we now have it, it totally makes sense to use the original package.
Hey! I’m Kamil from Software Mansion and I would like to work on this task.