Add a global error page for unhandled route errors and 404s with a link back to the marketplace

[Chucks1093]

Summary

Navigating to an unknown route or encountering an unhandled error currently shows a blank page. A global error page with a clear message and a 'Go to Marketplace' button would prevent users from feeling lost and reduce bounce rate.

Scope

• Add a 404 page rendered for any unmatched route with message 'Page not found'
• Add a global error boundary at the router level catching unhandled render errors
• Both pages show a 'Go to Marketplace' button that navigates to the marketplace
• Log unhandled render errors to the existing client-side error logger before showing the error page
• 404 page should not log to the error logger (expected user behaviour)

Acceptance Criteria

• Unmatched route renders 404 page with correct message
• Unhandled render error renders error page
• 'Go to Marketplace' button navigates correctly on both pages
• Render errors logged to client-side logger
• 404 visits not logged to error logger

ETA: 12 hours

---

Coordinate on Telegram

[Ssoleed]

@Ssoleed has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainer can I be assigned to this issue?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ssoleed to this issue.

[muizbolaji4]

@muizbolaji4 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainer, This issue matches my experience, and I'd appreciate the opportunity to work on it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @muizbolaji4 to this issue.

[Lspnjr1]

@Lspnjr1 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainers,
I’m Lspnjr1
I would like to be assigned to this issue. After reviewing the requirements, I’m confident that I understand the scope of the task and the project’s contribution criteria. I believe I can deliver a clean, maintainable implementation that aligns with the project’s standards.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Lspnjr1 to this issue.

[Godswillopeyemihub]

@Godswillopeyemihub has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello! I’d love to take on this issue. I’ve reviewed the requirements and have a clear path forward for the implementation. Could you please assign this to me?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Godswillopeyemihub to this issue.

[Tonyfash]

@Tonyfash has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I've taken the time to understand the scope of this issue and would appreciate the opportunity to contribute.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Tonyfash to this issue.

[drips-wave]

Congratulations, @Ssoleed! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Ssoleed: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊