react-strict-dom

Summary This change replaces the suppressions with real types, moves the prop-building mutation out of the hook bodies so it stops fighting the React hook rules, and pins the result down with Flow tests. This is a types-only change. It does not alter runtime behavior, so it can land on its own and be reviewed as such. Motivation is a checked-in promise to come back later. For the event props it had two costs: 1. No checking on handler arguments. typed clean. 2. No editor autocomplete on the event payload, so authors guessed field names or read the source. The props are the public surface of the library. They are the right place to spend the type budget. What changed Event payloads are typed. A new module holds the event shapes the native factories actually construct: , , key, , and image /. Handlers whose runtime shape is defined by the platform (most pointer, mouse, touch, and clipboard events) use a single instead of . The payload types are re-exported from the native and web entry points so consumers can annotate their own handlers. Prop mutation moved out of the hooks. The native factories build their by mutating an object (role defaults, the emulation, the polyfill). Doing that inside a hook body needed a suppression. That logic now lives in plain helpers (, ) that take the and write to it directly, so the suppressions are gone. routes through the type boundary.** now exports from How this improves DX Event handlers are checked. A typo in a payload field or a wrong handler signature is a Flow error at the call site, not a runtime surprise. Editors autocomplete the payload fields, so authors stop reading the source to find out what hands them. The payload types ship from the package entrypoints, so a consumer can write and have it stay in sync with the library. The hook bodies read as straight data flow now. The mutation helpers say what they own in their signatures instead of leaning on per-line suppressions. Type safety in practice A typo in a payload field is a Flow error where it is written, not a runtime : The click payload carries the modifier and position fields it actually has, so reaching past them is caught: Key handlers get a stable field across platforms: Annotating a handler defined outside JSX uses the exported payload types, which stay in sync with the library: A handler whose signature does not match the prop is rejected, so a web payload shape cannot be assumed on a strict element: The opaque handlers still pass the event through, but forces a check before use rather than handing back : Compat Table means the native runtime wires the handler today; means the type exists and the event passes through, but no native module wires it yet. Notes for reviewers A few calls I would like a second opinion on: 1. The exported payload types (, ...) are new public API. If the names or shapes are wrong, now is the time to change them. 2. Should the re-synthesized and pass-through handlers get concrete payload types now, or stay opaque until a native implementation wires each one?

Describe the issue Hi! The good ol' regular documentation website is now redirecting to https://opensource.fb.com/. Expected behavior https://facebook.github.io/react-strict-dom should not be redirecting to the meta open source landing page. Steps to reproduce Try to access https://facebook.github.io/react-strict-dom Test case _No response_ Additional comments _No response_