为何`react-native-reanimated`从插值器中移除？相关问题咨询

Why was react-native-reanimated removed from interpolators? #

Hey there, I totally get the frustration of digging through a commit and not finding the "why" behind a change. Let me break down what I know about this:

• That specific commit is mostly focused on code implementation, so it doesn’t spell out the reasoning directly. But from React Navigation v5’s overall design shift: the team wanted to build a more flexible, lightweight animation system. By removing the hard dependency on react-native-reanimated, they made the core library less tied to third-party tools, letting developers choose their preferred animation library (you can still manually integrate react-native-reanimated with v5 if you need it!).
• Back when v5 was being developed, react-native-reanimated had some compatibility hiccups with certain React Native versions. Cutting the dependency helped streamline the core library’s stability and reduce potential conflict points.
• For more official context, you might want to check the v5 release announcements or migration guides—those docs usually call out big dependency changes like this, even if individual commits don’t.

Where did the v5 roadmap Issue go? #

You’re not imagining it—there absolutely was a v5 roadmap Issue at one point! Most likely, it’s been archived, closed, or rolled into the project’s milestones as the version moved from planning to release. Open-source projects often move roadmap discussions out of Issues once features are finalized to keep the Issue tracker focused on active bugs and requests.

• You can check the project’s milestones section (filter for v5-related entries) to see the planned features and progress tracking that was originally in the roadmap Issue.
• The official React Navigation v5 docs might also have a "What’s New" or "Goals" section that outlines the core priorities from the original roadmap.

内容的提问来源于stack exchange，提问作者Trevor