[GOOD FIRST ISSUE] Add error boundary to Dashboard route

[Priyanshu-byte-coder]

What Needs to Be Done

Add a React Error Boundary to the Dashboard page so that if any widget crashes, it shows a friendly error message instead of crashing the entire page.

Why This Matters

Currently, if any dashboard component throws an error (e.g., bad API response, rendering bug), the entire dashboard goes blank. An error boundary catches the error and shows a fallback UI while keeping the rest of the page functional.

Files to Look At

• src/app/dashboard/page.tsx — Dashboard page layout
• src/app/dashboard/error.tsx — Create this file (Next.js App Router error boundary convention)
• src/components/ — Dashboard widget components

Acceptance Criteria

• Create src/app/dashboard/error.tsx following Next.js App Router conventions
• Error boundary shows a user-friendly message with a "Try Again" button
• Styling matches existing dashboard theme (use CSS variables like var(--card), var(--foreground))
• Error is logged to console for debugging
• "Try Again" button calls the reset() function to retry rendering

Tech Context

Next.js App Router uses file-based error boundaries. Create an error.tsx file that exports a client component with error and reset props. See Next.js Error Handling docs.

Mentorship

Comment on this issue and you'll receive guidance on getting started. The maintainer will help you through your first PR.

[Mahesh-forcode]

@Priyanshu-byte-coder I'm a GSSoC Contributer and I want to contribute on this repo by solving this issue
please assign me

[github-actions]

Assigned to @Mahesh-forcode! You have 7 days to open a PR. No PR after 7 days = auto-unassigned so others can pick it up. Good luck!

[VIDYANKSHINI]

Hi @Priyanshu-byte-coder,

I would like to work on this issue under GSSoC'26.

Plan of approach:
• First, analyze the current dashboard route structure in src/app/dashboard/page.tsx and identify all widget-level error risks
• Create src/app/dashboard/error.tsx using Next.js App Router error boundary pattern
• Implement a clean fallback UI with proper styling using existing CSS variables (var(--card), var(--foreground)) so it matches the dashboard theme
• Add a user-friendly error message with a "Try Again" button that correctly triggers the reset() function
• Ensure errors are logged for debugging while keeping UI stable
• Test by forcing errors in a sample widget to confirm only affected components fail, not the entire dashboard

I have already contributed to this repository and completed a previous assigned issue (currently under review). I would be happy to take this up since I’m not holding any active tasks right now.

Please assign this issue to me.

Thank you

[github-actions]

@VIDYANKSHINI This issue is already taken by @Mahesh-forcode. Check other open issues!

[github-actions]

Hey @Mahesh-forcode — this issue was assigned 7 days ago with no PR opened. Unassigning so others can pick it up.

Still working on it? Drop a comment and request re-assignment.