How are error boundaries handled in React v15?
Interviewer Expectations for this Question
01
Core Competency
Assesses fundamental understanding of React conventions, runtime behavior, and memory/performance considerations.
02
Evaluation Criteria
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Comprehensive Model Answer
Verified Solution
⚠️ LEGACY: This question is only relevant for historical context. React v15 is extremely outdated (released in 2016).
React v15 provided very basic support for _error boundaries_ using the unstable_handleError method. This was an experimental feature that was later redesigned and renamed to componentDidCatch in React v16.
Modern Error Boundaries (React 16+):
- Use
static getDerivedStateFromError(error)for UI fallback - Use
componentDidCatch(error, info)for logging - Work consistently across server and client rendering
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.