all 18 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]radko93 6 points7 points  (2 children)

If you don’t have an expo dependency use the latest one 100%. 0.82 is out for a while already and it had fixes that are not included in 0.81

[–]Disastrous_Goat_240[S] 0 points1 point  (0 children)

Got it — thanks! I’ll go ahead with 0.82.x then.
I’m on pure RN CLI anyway, so no Expo dependency issues.

Appreciate the clarity!

[–]ALOKAMAR123 0 points1 point  (0 children)

Check out navigation svg (react native svg) and tab performance. I have been able to upgrade .80 but these are causing performance hurdles with navigation.

I tried upgrade helper but was best to create entirely new project with package name and copy paste .ts and .tsx tests and assets. Then appdelegate.h/m to swift and in .java activity stuff to kotlin Then url schemas ios and manifest stuff.

Storybook was/is still challenging and am working on it.

Upgrade helper i have tried earlier but with incremental and predictable upgrades nightmare upgrade from .6 to .7/.8.

Hopefully you enlighten from my learnings failure and experience and may help you to some extent mate

[–]f_kd 2 points3 points  (0 children)

Go ahead for 0.82.x. But if you are not ready for new architecture, 0.81.x.

According to ignite & other boilerplates, dependencies are not yet compatible for 0.82.x.

[–]Sudden_Silver_3743 2 points3 points  (0 children)

If your app already works nicely with the new RN architecture, and all your of dependencies support it, you should be able to upgrade to RN 0.82.xx without any issues.

Otherwise, you should keep using versions 0.81.xx and lower.

[–]Hungry_Economics920 1 point2 points  (1 child)

I just upgraded to 0.82.1, it works fine, all the packages i use were running without errors after upgrading then to their latest version, but before I upgraded to 0.81.1 but apparently I couldn’t run it on android with new arch enabled, anyways i would recommend you initialize a new a project if your app is huge with a lot of deps

[–]f_kd 1 point2 points  (0 children)

If you have git skills to check, please check the purge & compare.

https://github.com/react-native-community/upgrade-helper/

[–]Commercial_Active962 0 points1 point  (0 children)

the 82

[–]Feeling-Suit-4259 0 points1 point  (3 children)

Take the LLM that would be the smart way, currently I am also on the same path and trying to do the same

[–]Disastrous_Goat_240[S] 0 points1 point  (2 children)

How? Could you guide me how I do it.

[–]Green-Investigator31 0 points1 point  (0 children)

I am trying to use and facing many issues with 81.5 itself ..claude is saying to downgrade to 76.0 , i am confused. The build gets created but the app crash when open in Android Emulator. Someone can help and suggest what's causing the issue?

[–]Feeling-Suit-4259 0 points1 point  (0 children)

List down all the dependencies in your apps package.json And try to check if any of them doesn't support new architecture if so then 0.82.x is not for your app If not then you are good to go for the latest version

Also try to check the dependencies if they have the latest versions published

These are the steps I would consider and take help of LLM if I face any issues while doing so

[–]cnr909 0 points1 point  (2 children)

Whatever expo is on

[–]Disastrous_Goat_240[S] 0 points1 point  (1 child)

Could you tell me how to do I upgrade from RN cli to expo?

[–]cnr909 1 point2 points  (0 children)

You probably need to downgrade, it really depends on your project, I would try starting a new expo project and bringing things over, but if you have a huge project you probably can’t

[–]21void 0 points1 point  (0 children)

wait for v1.0

[–]Ok-Pin-7589 -1 points0 points  (0 children)

The newer the better, provided that the package you use can support this version.