Moving from Expo v36 to the latest will take some time but it is doable.

The "official way" would be to incrementally upgrade to v37, v38, v39 ...., v49. But a problem with that is that everything before v46 is no longer actively supported.

When I upgraded from v35, I did it one version at a time until v40, then I was able to jump a few versions at a time. That was 2 years ago. I just don't know if that is worth doing all the way back to v36.

If this were me, I'd likely create a brand new Expo project with the latest-n-greatest (npx create-expo-app <YOUR_PROJECT_NAME_HERE>), copy the files from your old project's src folder to the new folder, for each of the dependencies of your old project listed in package.json I'd install them into the new project using npx expo install <.....> (probably best one at a time).

You might take this upgrade as an opportunity to update some of your code. Some of those older react-native-.... dependencies might now be deprecated or superceded by newer libraries...possibly even some Expo-specific ones.

One thing to note from your original project: you have a number of NPMs installed as dependencies that really should be devDependencies instead. The difference is whether you install them using npx expo install .... or npx expo install --save-dev ..... dependencies are for NPMs that are directly used by your app, whereas devDependencies are things used only during development, testing and build. For example, eslint and its plugins are almost certainly devDependencies for your app, not used inside your app itself.

As you are doing your upgrade, you might find that hanging out in the Expo Developers server on Discord is worthwhile. Lots of folks there who have been through these upgrades and have the scars to help you avoid the wounds.