[Issue]: Add error boundary for dynamic pages

[shreyashpatel5506]

Issue Type

Page Update

Issue Description

Next.js dynamic pages should handle 404/500 gracefully.

Expected Outcome

Implement error boundary at app level.

Additional Details (for Other / Bug / Backend)

Suggested files: app/error.js / app/not-found.js

[waleedahmedwaheed]

I agree that this needs to be handled more gracefully. I can add proper error boundaries for dynamic pages so that 404 and 500 errors don’t result in a broken or confusing user experience.

I’ll implement this at the app level using Next.js conventions by adding app/error.js for runtime errors and app/not-found.js for missing routes or invalid dynamic params. This will ensure users see clear, user-friendly fallback pages instead of unhandled errors.

Once implemented, dynamic routes will handle failures more cleanly and consistently across the app.

[shreyashpatel5506]

@waleedahmedwaheed
If you find this repository helpful, please consider giving it a ⭐. Your support really motivates me and helps the project reach more people.

[shreyashpatel5506]

@waleedahmedwaheed, do you work on this issue?