feat: implement generic React Error Boundaries to prevent full app unmounts on component failure

[nitishchaubeyy]

Description

This PR addresses #434 by implementing route-level React Error Boundaries. Previously, an unexpected error (like malformed API data or a null Firestore snapshot) in any leaf component would crash the entire React application tree, resulting in a white screen.

Key Additions

• ErrorBoundary.jsx Component: Created a reusable, Framer-Motion animated Class Component to catch child render errors safely. It provides a polished "Something went wrong" card UI.
• State Recovery Mechanism: The boundary includes a "Try Again" button that triggers this.setState({ hasError: false }) to remount the child tree without forcing a hard browser refresh.
• Route Integration: Created a withErrorBoundary higher-order helper to wrap all dynamically imported lazy routes in AppRoutes.jsx with context-specific fallback messages (e.g., "GitRank couldn't load right now...").
• Dev DX: Added a conditional block that explicitly renders the raw .toString() error output in NODE_ENV === 'development' to aid debugging.

Fixes #434

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ranker-hub	Ready	Preview, Comment	Jun 11, 2026 9:00am