react-hooks-js/todo
Unimplemented features
- Category: React Compiler
- Severity: error
- Source:
eslint-plugin-react-hooks - Framework: global
- Enabled when: eslint-plugin-react-hooks v6+ installed AND React Compiler detected in project
- Documentation: https://react.dev/reference/eslint-plugin-react-hooks
Validate the diagnostic
Confirm the reported code matches this rule before you edit it.
Hint-severity diagnostic the Compiler emits when it bails on a feature it should support but has not yet implemented — not a code mistake, more of a 'Compiler cannot optimize this yet' notice. There is no rule-level true/false positive distinction: every diagnostic is a real Compiler limitation rather than a defect in your code.
How to fix
Follow the rule guidance while preserving unrelated behavior.
Copyable fix prompt
Copy this self-contained prompt into your coding agent after you confirm the diagnostic.
Refactor the affected code into a shape the Compiler supports today (often hoisting an inner function, splitting a giant component, or removing a dynamic pattern). If a workaround is not feasible, add a 'use no memo' directive at the top of the file so the Compiler skips it, and check the React Compiler issue tracker for an open ticket covering your pattern. See https://react.dev/reference/eslint-plugin-react-hooks
Related rules
More React Compiler rules from the rules reference:
react-hooks-js/unsupported-syntax: Validates against syntax that we do not plan to support in React Compilerreact-hooks-js/use-memo: Validates usage of the useMemo() hook against common mistakes. See [`useMemo()` docs](https://react.dev/reference/react/useMemo) for more information.react-hooks-js/void-use-memo: Validates that useMemos always return a value and that the result of the useMemo is used by the component/hook. See [`useMemo()` docs](https://react.dev/reference/react/useMemo) for more information.react-hooks-js/component-hook-factories: Deprecated: this rule has been removed in 7.1.0.react-hooks-js/error-boundaries: Validates usage of error boundaries instead of try/catch for errors in child components