Reanimated

[thomasttvo]

Reanimated implementation is here and now with almost all features preserved. Some features like pin onPress/onLongPress need to be stripped due to time constraint.

---

Note

Migrates the zoomable view to a Reanimated + Gesture Handler implementation with worklet-driven callbacks and smoother animations; updates the example app and tooling to support the new stack.

• Core: Replaces legacy Animated/pan logic with Reanimated shared values, worklets, and Manual gesture handling; adds onTransformWorklet and onStaticPinPositionMoveWorklet, preserves double-tap/pinch/shift behavior, and refines static pin updates
• Example: Refactors to Reanimated (marker scaling via animated style), adds long-press alert and optional Modal wrapper, removes old zoomAnimatedValue
• Tooling: Adds Reanimated Babel plugin; updates Metro config to alias src and avoid peer duplicates; bumps example to Expo 54/React 19/RN 0.81 and adds react-native-reanimated/gesture-handler/worklets; minor style/tsconfig tweaks

^{Written by Cursor Bugbot for commit 490ae19. Configure here.}

[elliottkember]

This is looking really great — amazing work. The performance gains from things like worklets will be out of this world.

We may need to make some minor changes in our app to implement this but they should be small fry compared to these changes.

[elliottkember]

This will probably be the tricky part in our internal implementation of this. I've never truly liked the way this component takes an animated value as a prop, this is how we ended up with sheet zoom contexts where other components need to know about zoom as it happens and we needed an HOC with the animated zoom value.

It seems like an imperative handle is probably the way to do this, plus maybe some built-in components for handling interpolations — or perhaps just a context provided by this component to its children.

[elliottkember]

Yeah these kind of props sort of break the whole magic of reanimated and animated values huh?

Do we use this, or can we just subscribe to the animations and react with animated components?

I think this will maybe just be a huge major version release with lots of breaking changes that remove footguns

[cursor]

Comment @cursor review or bugbot run to trigger another review on this PR

[thomasttvo]

bugbot run

[cursor]

✅ Bugbot reviewed your changes and found no bugs!

---

Comment @cursor review or bugbot run to trigger another review on this PR

[elliottkember]

I noticed that the example and base repos have different versions of reanimated. This is a good thing, I think — it shows that the library works on both versions. But when I went to refactor runOnJs to scheduleOnRN because of a deprecation warning in Reanimated 4, I noticed that it's only deprecated in the example app.

Might be worth using the same version in both... or maybe even having two example apps for testing both reanimateds at once??

~/Sites/react-native-zoomable-view elliott/thomas-reanimated-runonjs • yarn why react-native-reanimated |grep Found
=> Found "react-native-reanimated@3.16.7"
~/Sites/react-native-zoomable-view elliott/thomas-reanimated-runonjs • cd example && yarn why react-native-reanimated |grep Found
=> Found "react-native-reanimated@4.1.6"

[elliottkember]

Clever! I think this should exhibit the same behaviour as the react-navigation / react-native-screens pull to close, but I might add the routing library and some formSheet / pageSheet routes just to test the theory

[elliottkember]

🥳 Looks good with expo-router, which uses native-stack under the hood!