Test enabling react-native-nitro-fetch

[roryabraham]

Coming from https://expensify.slack.com/archives/C035J5C9FAP/p1776097010691589

Let's try enabling react-native-nitro-fetch and measure the performance impact to evaluate if it's worth proposing to add on main.

Issue Owner

Current Issue Owner: @chrispader

[munsuyog]

@roryabraham Can you please allow me to work on this?

[chrispader]

@roryabraham commenting for assignment, i can start working on this!

[roryabraham]

@munsuyog thanks for your interest, but @chrispader works at Margelo, the agency that built and maintains react-native-nitro-fetch, so I'm assigning to him

[chrispader]

Started working on these two PRs:

• Actual changes: [WIP] feat: Enable react-native-nitro-fetch #88110
• PR for testing and benchmarking: [WIP] feat: Test and benchmark react-native-nitro-fetch #88111

[chrispader]

Quick update on this issue:

• I had to update quite a few of other dependencies to make everything compatible with latest Nitro Modules version. This meant, bumping react-native-worklets, which also required bumping react-native-reanimated and expo-modules-core because of peer dependency requirements
• Because of the above, i based [WIP] feat: Test and benchmark react-native-nitro-fetch #88111 on this Onyx bump PR, which already includes the updated NitroModules and NitroSQLite versions.
• I have not started any benchmarks or testing on [WIP] feat: Test and benchmark react-native-nitro-fetch #88111 yet, but i already got it to build successfully.

Next steps:

• Check for best spots to "prefetch" queries on application start, to improve startup time.
• Create benchmarks for app startup time metrics.
• Investigate whether we want to migrate Pusher WebSockets implementation to react-native-nitro-fetch as well. This would probably involve a bigger effort though, so we would want to think about this more deeply.

@roryabraham going to continue working on this this week and it's one of my higher priorities!