Skip to content

fix: Fix not found error handling and rendering errors server side#72

Merged
KyleJune merged 1 commit intomainfrom
dev
Jan 30, 2026
Merged

fix: Fix not found error handling and rendering errors server side#72
KyleJune merged 1 commit intomainfrom
dev

Conversation

@KyleJune
Copy link
Member

Summary

Locally I had issues with one of my error boundaries not picking up errors. I found that a recent PR introduced an issue where it wasn't handling not found errors correctly. The client side needs catch all routes so that the error will be bound to the correct boundary and createErrorContext needed to be updated to not recreate the static handler to avoid hydration errors. Before this fix, the top level error boundary would catch all errors caused by routes not being found.

@KyleJune KyleJune merged commit 50ea639 into main Jan 30, 2026
9 checks passed
@KyleJune KyleJune deleted the dev branch January 30, 2026 03:27
KyleJune pushed a commit that referenced this pull request Jan 30, 2026
## [0.3.1](0.3.0...0.3.1) (2026-01-30)

### Bug Fixes

* Fix not found error handling and rendering errors server side ([#72](#72)) ([50ea639](50ea639))
@github-actions
Copy link

🎉 This PR is included in version 0.3.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant