Library Authors: When You Actually Need Overrides
What You'll Learn
You'll understand the extremely rare situations where violating the Rules of Hooks is technically necessary and safe for advanced library code.
The Exceptional Cases
Throughout this phase, we've hammered home that the Rules of Hooks are inviolable. That's true for 99.9% of React code. But there's a tiny exception: library authors writing framework-level code sometimes need controlled rule violations.
Think of it like "Employees Only" areas in a theme park. Guests (application developers) should never go there. But maintenance staff (library authors) occasionally need access to keep the machinery running.
When Overrides Are Legitimate
You might need ESLint overrides if you're:
- Building React itself — React's internal code doesn't always follow its own public rules because it manages the hook registry directly
- Creating dev tools — Testing utilities that inspect or mock hook behavior need to break rules in controlled environments
- Writing framework adapters — Code that bridges React to other systems might require non-standard hook patterns
What This Looks Like
// ONLY in library code, with extreme caution
function internalTestHelper() {
// eslint-disable-next-line react-hooks/rules-of-hooks
const value = useState(0);
// ... controlled violation for testing infrastructure
}
The Critical Distinction
Application code should NEVER use these overrides. If you're building a feature for your app and think you need to break the rules, you're solving the wrong problem. Framework authors accept the risk because they're providing infrastructure; you're building on that infrastructure.
Key Takeaway: Legitimate rule violations exist only in framework internals, dev tooling, and advanced library code. Application developers should treat the Rules of Hooks as absolute — no exceptions, no shortcuts.