Avoid ReactDOM.findDOMNode
`findDOMNode` reaches through component boundaries with a deprecated escape hatch that breaks strict mode migrations.
#Metadata
#Why it matters
Direct DOM lookups make React trees harder to refactor and fail to model multi-node or fragment-based rendering safely.
#Remediation
Attach a ref directly to the rendered element, or forward refs through component boundaries instead of reading DOM nodes imperatively.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/typescript/ts.react.no-find-dom-node.rule.yaml.