Skip to content

docs(linter): Clarify the no-find-dom-node rule with a note that the method was removed in React 19. #18556

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
graphite-app merged 1 commit into from
Jan 26, 2026
Merged

docs(linter): Clarify the no-find-dom-node rule with a note that the method was removed in React 19. #18556

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions crates/oxc_linter/src/rules/react/no_find_dom_node.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,13 +21,16 @@ pub struct NoFindDomNode;
declare_oxc_lint!(
/// ### What it does
///
/// This rule disallows the use of `findDOMNode`.
/// This rule disallows the use of `findDOMNode`, which was deprecated in 2018 and removed in React 19.
///
/// ### Why is this bad?
///
/// `findDOMNode` is an escape hatch used to access the underlying DOM node.
/// In most cases, use of this escape hatch is discouraged because it pierces the component abstraction.
/// [It has been deprecated in `StrictMode`.](https://legacy.reactjs.org/docs/strict-mode.html#warning-about-deprecated-finddomnode-usage)
/// It has been deprecated for years, and was
/// [removed from React entirely in React 19](https://react.dev/blog/2024/04/25/react-19-upgrade-guide#removed-reactdom-finddomnode).
///
/// It should not be used.
///
/// ### Examples
///
Expand Down
Loading