GeezerVison

Upgrade the bindings to [email protected], plus a pass on events, elements and refs. Bindings were checked against the generated types of [email protected]. One commit per topic, each commit builds on its own.

React Native 0.86

• Breaking: BackHandler.addEventListener handler receives a hardwareBackPressEvent (type_, timeStamp) instead of unit
• Style.blendMode: add #"plus-lighter"
• Pressable.rippleConfig: add alpha; TouchableNativeFeedback.Background.ripple takes a Color.t (accepts PlatformColor)
• TextInput.autoComplete: new Android autofill hints, plus values that were already missing (current-password, new-password, given-name, …)
• peerDependencies: react-native >= 0.86.0
• No new deprecation affects the bindings (ViewUtil.getUIManagerType is native Android, setComponentProviderInstrumentationHook isn't bound)

Fixes

• Breaking: synthetic events target and currentTarget are native elements (DOMAPI.anyElement), not numbers. The renderer sets them to the element's public instance since the new architecture (the only one since RN 0.82), and the web-based event dispatching of RN 0.88 keeps them as elements.
• Breaking: getBoundingClientRect returns a Layout.domRect (x, y, width, height, top, right, bottom, left), it was typed as Rect.t
• Add Rect.size to pass a number to hitSlop / pressRetentionOffset

Events

• Generic Event.syntheticEvent<'payload> / Event.responderSyntheticEvent<'payload> records with Event.Methods / Event.ResponderMethods
• Event.SyntheticEvent / Event.ResponderSyntheticEvent functors stay the public API to define an event module, now built on these records: events of third-party bindings share the same type and get new methods for free
• Breaking: bubbles, cancelable, defaultPrevented, eventPhase, isTrusted and type are option<…> (undefined while the handler runs, never null; event pooling errors stay explicit, see Event.layoutEvent needs to be Js.Nullable.t #832)
• Breaking: the nativeEvent getter returns the payload type instead of 'a

Elements and refs

• Element methods are generic externals on DOMAPI.element<'nativeElement>. Component-specific methods are restricted by the element kind ([> #scrollView], [> #textInput], …): FlatList gets the ScrollView methods, TextInput doesn't. No more *Methods.Make functor applied at runtime.
• NativeElement.Impl stays the public API to define an element module, now based on NativeElement.Methods
• DOMAPI.Node.Impl takes a type constructor so node methods are written once; DOMAPI.Element accepts any element
• Typed useRef in every element module: let ref = TextInput.useRef(), compiled to React.useRef(null)
• Ref.t is the object ref type: pass it directly (ref=myRef), and the generated JS no longer wraps it in Primitive_option.some. Add Ref.callbackWithCleanup (React 19). Ref.value / Ref.valueRef are deprecated.
• Breaking: remove the internal NativeMethods.Make / *Methods.Make functors, DOMAPI.Element.Impl, and the deprecated NativeElement.element / NativeElement.ref types

Notes for reviewers

• npm test passes (clean build, warnings as errors). Changes were checked by compiling throwaway usage files and reading the generated JS; nothing was run in a real React Native app.
• Third-party bindings of the org (safe-area-context, flash-list, rescript-react-navigation) were compiled against this branch and still build (react-navigation has its own unrelated Js.* deprecation warnings with ReScript 12).
• Public functors (NativeElement.Impl, Event.SyntheticEvent) are kept on purpose as a stable API for third-party bindings, even though applying them costs one empty function call per module at load.
• The website still uses Ref.value in scrollview.md, to update separately.
• package.json version is still 0.85.0, to be bumped in the release commit.

🤖 Generated with Claude Code