Strip complicated but low priority features ahead of reanimated conversion

[thomasttvo]

Since we'll convert to reanimated in a later PR, it's important to strip some features to avoid a complicated migration. We can always reintroduce them in the reanimated world if we need to.

Note

Remove pan-boundary/momentum and pin animation features, simplify offsets/gestures, and update API, docs, and builds accordingly.

• Core changes:
  • Remove pan-boundary logic, momentum decay, and pin animations; simplify offset handling and gesture flow; delete applyPanBoundariesToOffset and related animation helpers.
  • Modernize code (optional chaining, JSX runtime) and streamline internal state.
• API/Props:
  • Drop bindToBorders, panBoundaryPadding, disableMomentum, and animatePin; remove pinAnim from StaticPin; methods no longer accept bindToBorders params.
  • Update typings and d.ts accordingly; add useLatestCallback hook.
• Docs/Examples/Build:
  • Revise README tables/usages and example app to reflect removed props.
  • Keep only getZoomToAnimation in animations; add package type fields in build outputs.

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

[cursor]

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

[cursor]

TypeScript types include removed prop causing silent failure

The panBoundaryPadding prop remains in the TypeScript interface definition, but the implementation has been completely removed (the applyPanBoundariesToOffset helper file was deleted and all related logic stripped out). TypeScript users can pass this prop without compilation errors, but it will be silently ignored at runtime. This causes unexpected behavior for users who set panBoundaryPadding expecting it to control pan boundaries.

Additional Locations (1)

• lib/typescript/typings/index.d.ts#L27-L28

 

[elliottkember]

I think this should be fine, but it's a breaking change so we'll need a minor version, and a CHANGELOG.md or some kind of breaking change notice in the release. I'll be interested to see whether anybody is using these features and has trouble upgrading

[thomasttvo]

@elliottkember that's a good point. I've created this PR to create a better setup for changelog generation. We can edit the changelog (once it's generated) to explain further which features have been dropped once we publish. Additionally, we can also publish this as part of an RC version together with the reanimated stuff and ask the community for feedback before turning it into a official version

[elliottkember]

@thomasttvo Sounds like a plan. It may actually be worth making a new major version RC. Given the scope of the reanimated change I think it's justified, and will avoid anybody accidentally updating their if they use ^2 in package.json.