Cross-platform DOM Node API support with React Native 0.82

[yaminyassin]

React Native 0.82 introduces native DOM Node APIs on host elements. This is a significant milestone for React Strict DOM, as DOM traversal APIs are explicitly called out in the design goals as a key enabler for the project's approach.

I'd like to discuss how RSD can take advantage of these new native capabilities.

RSD currently polyfills several of these APIs in useStrictDOMElement.js by wrapping native nodes in proxy objects (e.g., getBoundingClientRect with viewport scaling, nodeName, layout length properties). With RN 0.82, some of this work may now be handled natively.

[MoOx]

Interesting topic indeed. I've been using RSD in production and really appreciate the project. That said, I've noticed activity has slowed down while there are still exciting areas to explore (SVG support, stronger TypeScript types, etc.). @necolas would you mind sharing any thoughts on the roadmap or what's ahead for RSD? Would love to know how the community can best contribute.

[yaminyassin]

Opened a PR that adopts the RN 0.82 DOM Node APIs as the base for useStrictDOMElement: #475.

here's a few changes:

• Peer dep react-native bumped to >=0.82.0.
• useStrictDOMElement rewritten to wrap the underlying RN host node in a thin Proxy instead of cloning it via Object.create + Object.defineProperties.

Happy to iterate on the design if maintainers want a different shape (e.g. pointer-capture wiring, narrowing the wide-spread onto exact ImageProps/TextInputProps host types, etc.). Follow-up items are listed in the PR description.

[yaminyassin]

PR merged!