Should I rewrite all class components in a legacy codebase?
No. If a class component works and is not changing, leave it. Rewriting working code introduces risk without value. Convert when you are already modifying a component for another reason, so you modernize incrementally.
Verify This Answer
Cross-check this information using these trusted sources:
More FAQs in Best Practices for Working With React Class Components in Legacy Code
When you are already touching the component for a feature or bug fix. Convert it at the same time so you modernize the codebase incrementally without a risky big-bang rewrite. Avoid converting stable, untouched components.
Preserve behavior exactly. Map lifecycle methods to useEffect carefully, get the dependency array right, and test that the converted component behaves identically to the original. Use the hooks lint plugin to catch dependency mistakes.
No. Isolate risky changes like conversions in their own commit or PR with tests. Do not bundle a conversion with unrelated changes, so reviewers can focus on whether behavior is preserved.
Still have questions?
Browse all our FAQs or reach out to our support team