-
-
Notifications
You must be signed in to change notification settings - Fork 237
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v4] Should react-native-reanimated be an optional peer dependency? #889
Comments
Related to In order to provide greater adoption, does it make sense to open it up a bit? |
In my opinion, if someone is bothering to use Nativewind 4, especially in its current pre-release state, then they should definitely be on @latest for React Native Reanimated. |
I tend to agree with you, but when working on a production app used by many distributed component teams, it's not as easy as seems to just force latest. If the API and features of a 3rd party module are the same across many versions (even majors like react-native-reanimated), a library consuming that module should support the minimum version via peer deps. This helps greatly with adoption of the library too. But this thread is more about react-native-reanimated being a peer dependency, regardless of version 😄 |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
If I never use the animated classes, I won't need
react-native-reanimated
to be available and built in my native app. However, I will continuously get unmeet peer dependency warnings until I add it, which means it'll autolinked and built with my app.I noticed that it used to be an optional peer dependency, but is now required.
How is
react-native-reanimated
different thanreact-native-svg
andreact-native-safe-area-context
, which are optional?Thanks!
The text was updated successfully, but these errors were encountered: