feat: Add ErrorBoundary and RouterError for better error UX (#1185)#1186
Conversation
Implement #1185: Provide ErrorBoundary and errorElement to catch and display application errors gracefully. - Add ErrorBoundary component to catch React component render errors - Add RouterError component to catch React Router v6 data router errors - Wrap RouterProvider with ErrorBoundary in main.tsx - Add errorElement to root route in router This provides a better user experience when the application encounters errors, showing a user-friendly error page with options to reload or go back instead of the default React error screen. Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
|
@copilot Please review this pull request. |
I found one material issue: |
Security fix for PR #1186: ErrorBoundary was leaking internal implementation details (stack traces, error messages) to end users in production. - Gate error details section to development mode only using import.meta.env.DEV - In production, only show generic error message and reload button - Prevents information disclosure while maintaining debugging capability in dev Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
|
@copilot Please review this pull request. |
I reviewed the current diff and found one remaining material issue: |
Implement #1185: Provide ErrorBoundary and errorElement to catch and display application errors gracefully.
This provides a better user experience when the application encounters errors, showing a user-friendly error page with options to reload or go back instead of the default React error screen.