Coming from this proposal
Background
react-native-reanimated is our core animation library. We’re currently on v3.19.1. v4 is essentially the continuation of v3: same implementation, but focused solely on the New Architecture and introducing new features. It also formalizes the split into two packages: react-native-reanimated and react-native-worklets.
Problem
Reanimated v3 is already effectively unsupported, no new features are added (only patch releases on request). Staying on v3 means we miss out on ongoing improvements, optimizations available only in v4, and risk falling behind as the ecosystem standardizes on v4.
Solution
Let’s bump to Reanimated v4. This will:
- Keep us current with the actively supported version and aligned with the ecosystem.
- Enable new optimization options on Android (issue with benchmark)
- Drop two patches (dontWhitelistTextProp.patch and correctly-handle-Easing.bezier.patch)
- Allow us to remove the direct Reanimated dependency in react-native-live-markdown by switching it to react-native-worklets
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021961167667293267879
- Upwork Job ID: 1961167667293267879
- Last Price Increase: 2025-08-28
Issue Owner
Current Issue Owner: @abekkala
Issue Owner
Current Issue Owner: @blazejkustra
Issue Owner
Current Issue Owner: @blazejkustra
Coming from this proposal
Background
react-native-reanimated is our core animation library. We’re currently on v3.19.1. v4 is essentially the continuation of v3: same implementation, but focused solely on the New Architecture and introducing new features. It also formalizes the split into two packages: react-native-reanimated and react-native-worklets.
Problem
Reanimated v3 is already effectively unsupported, no new features are added (only patch releases on request). Staying on v3 means we miss out on ongoing improvements, optimizations available only in v4, and risk falling behind as the ecosystem standardizes on v4.
Solution
Let’s bump to Reanimated v4. This will:
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @abekkalaIssue Owner
Current Issue Owner: @blazejkustraIssue Owner
Current Issue Owner: @blazejkustra