fix: preserve original error in async component loading #232
+8
−4
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
This PR fixes an issue where original error information was lost when async component loading failed. Previously, when an async component threw an error, the error handler would catch it but throw a new error without preserving the original error message, making debugging difficult.
Changes Made
route-transition.tsto capture and include the original error message in the new errorroute-transition.test.tsto verify that the original error is preservedRelated links
N/A
Checklist