-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
fix: properly catch top level await errors #16619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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 |
|
Can we add a test for this? |
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();
} |
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 |
was just tinkering locally for my own curiosity (hadn't seen your reply), have a branch I can push up |
* use helper for async bodies * unused * fix * failing test + fix --------- Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>
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 test
and lint the project withpnpm lint