Conversation
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))
|
🎉 This PR is included in version 0.3.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.