fix: properly catch top level await errors#16619
Merged
Rich-Harris merged 3 commits intomainfrom Aug 18, 2025
Merged
Conversation
async errors within the template and derived etc are properly handled because they know about the last active effect and invoke the error boundary correctly as a response. This logic was missing for our top level await output. Fixes #16613
🦋 Changeset detectedLatest commit: ab5aeda The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
|
Member
|
Can we add a test for this? |
Member
|
I wonder if we should helperise this, rather than leaning on the compiler. What if instead of this... async function $$body($$anchor, $$props) {
var $$unsuspend = $.suspend();
var $$active = $.active_effect;
try {
(await $.save(new Promise(async (_, reject) => {
console.log(1);
await Promise.resolve();
route.current = 'other';
route.reject = reject;
console.log(2);
})))();
if ($.aborted()) return;
var h1 = root();
$.append($$anchor, h1);
} catch($$error) {
if (!$.aborted($$active)) $.invoke_error_boundary($$error, $$active);
}
$$unsuspend();
}
export default function Child($$anchor, $$props) {
$.push($$props, true);
var fragment = $.comment();
var node = $.first_child(fragment);
$$body(node, $$props);
$.append($$anchor, fragment);
$.pop();
}...it was this? export default function Child($$anchor, $$props) {
$.push($$props, true);
var fragment = $.comment();
var node = $.first_child(fragment);
$.async_body(async () => {
(await $.save(new Promise(async (_, reject) => {
console.log(1);
await Promise.resolve();
route.current = 'other';
route.reject = reject;
console.log(2);
})))();
if ($.aborted()) return;
var h1 = root();
$.append(node, h1);
});
$.append($$anchor, fragment);
$.pop();
} |
Member
Author
|
Thought about this but assumed there's a reason that it's not like this already so I didn't change it. But can adjust |
Member
|
was just tinkering locally for my own curiosity (hadn't seen your reply), have a branch I can push up |
Member
* use helper for async bodies * unused * fix * failing test + fix --------- Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>
Rich-Harris
approved these changes
Aug 18, 2025
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.
async errors within the template and derived etc are properly handled because they know about the last active effect and invoke the error boundary correctly as a response. This logic was missing for our top level await output.
Fixes #16613
Before submitting the PR, please make sure you do the following
feat:,fix:,chore:, ordocs:.packages/svelte/src, add a changeset (npx changeset).Tests and linting
pnpm testand lint the project withpnpm lint