Skip to content

fix: add 404 Not Found page for invalid routes#498

Open
kunwarshivamjsr wants to merge 2 commits into
lovelymahor:mainfrom
kunwarshivamjsr:fix/404-not-found-page
Open

fix: add 404 Not Found page for invalid routes#498
kunwarshivamjsr wants to merge 2 commits into
lovelymahor:mainfrom
kunwarshivamjsr:fix/404-not-found-page

Conversation

@kunwarshivamjsr

Copy link
Copy Markdown

🐛 Fix: Add 404 Not Found Page for Invalid Routes

Closes #497

Problem

Visiting any invalid URL (e.g. /anythingrandom) showed a completely blank page with only the navbar visible. No error message or navigation guidance was provided to the user.

Solution

  • Created a new NotFound.js component in client/src/pages/
  • Added a catch-all route path="*" in App.js to render the 404 page
  • The page includes a clear message and a "Go Back Home" button

Screenshots

image

Type of Change

  • Bug fix

@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the Lovely Mahour's projects Team on Vercel.

A member of the Team first needs to authorize it.

@kunwarshivamjsr

Copy link
Copy Markdown
Author

Hey @lovelymahor! 👋

I've resolved the merge conflict in client/src/App.js and the branch is now clean with no conflicts. 🎉

This PR fixes issue #497 by adding a NotFound page for invalid routes, so users no longer see a blank screen when navigating to an undefined path.

The Vercel check requires authorization from your end — could you please approve the deployment and review this PR? 🙏

Contributing as part of GSSoC (GirlScript Summer of Code).

Thank you! 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Missing 404 Page - Blank screen shown for invalid routes

1 participant