Issues updating packages: reanimated 2.9.1 -> 3.02, expo 46 -> 48 #386
Answered
by
nandorojo
benrbowers
asked this question in
Q&A
Replies: 1 comment 1 reply
-
|
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
benrbowers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
TL;DR: Upgrading reanimated to v3 has snowballed into having to update most of my packages. Which starter repo should I be referring to for the latest recommended package versions and babel plugins?
I've been using solito + nativewind for a while on a cross-platform app. It's been pretty great so far, but I recently had to rewrite an animation-heavy component to use reanimated sharedValues instead of moti. I got it working on native, but then found out that it didn't work on web. It looks like reanimated doesn't officially support web until v3, and the version I had installed was 2.9.1, which is from the tailwind starter repo (https://solito.dev/tailwind).
I started the project using that repo around December or January, so it's definitely time to update some of the packages, but it has been a pain to get everything working again with updated packages. The main two issues seem to be:
I've tried updating my project to match the current state of the nativewind starter repo, but it seems that that may already be outdated.
Am I better off referencing the main solito starter repo for the recommended package versions and plugins? Is there a better strategy I should be using to update my packages other that just looking at the current repos?
Thanks in advance! 🙌
workspace:
Beta Was this translation helpful? Give feedback.
All reactions