Can I opt out of strict mode?

<StrictMode> lets you find common bugs in your components early during development process. Although the Strict Mode checks only run in development, they help you find bugs that already exist in your code but can be tricky to reliably reproduce in production. Strict Mode lets you fix bugs before your users report them.

1
Opting out of Strict Mode inside a tree wrapped in <StrictMode> is impossible. This gives you confidence that all components inside <StrictMode> are checked.
2
If two teams working on a product disagree on whether they find the checks valuable, they need to either reach a consensus or move <StrictMode> down in the tree.

Difficulty: 5/10

Topics: StrictMode, Legacy code, Performance

Scenario Questions

0-2 years experience

1
How would you enable React StrictMode in a new project, and what would you do if a third‑party component breaks because of it?
2
What happens if you wrap only part of your component tree with <React.StrictMode> versus wrapping the entire app?

2-5 years experience

1
You notice that after adding <React.StrictMode> the console shows duplicate useEffect calls. How would you debug this and decide whether to keep StrictMode enabled?
2
A teammate wants to opt out of StrictMode for a legacy component that uses unsafe lifecycle methods. How would you handle this trade‑off?
3
Explain the impact of StrictMode on concurrent features and why it might cause unexpected behavior in a feature‑flag rollout.

5-8 years experience

1
Design a migration plan to gradually introduce StrictMode across a large codebase with many legacy components. What steps and tooling would you use?
2
How would you assess the performance implications of keeping StrictMode enabled in production, and what metrics would you monitor?
3
If a critical performance bug appears only when StrictMode is on, how would you isolate the cause without removing the safety benefits for the rest of the app?

8+ years experience

1
At a company with multiple teams sharing a monorepo, how would you set a policy around StrictMode adoption, and what governance process would you put in place to handle opt‑outs?
2
Discuss the long‑term maintenance trade‑offs of permanently disabling StrictMode for a subset of components versus refactoring them to be compatible.
3
How would you evaluate the risk of legacy code that relies on deprecated lifecycles when planning a future upgrade to React 18 concurrent features, considering StrictMode constraints?

Follow-up Questions

❓What steps would you take to isolate a component that breaks under StrictMode?
❓How would you communicate an opt‑out decision to other engineers?
❓What metrics would you monitor to ensure StrictMode isn’t hurting performance?