Skip to content

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

Merged
merged 3 commits into from
Aug 18, 2025

Conversation

dummdidumm
Copy link
Member

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

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • Prefix your PR title with feat:, fix:, chore:, or docs:.
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.
  • If this PR changes code within packages/svelte/src, add a changeset (npx changeset).

Tests and linting

  • Run the tests with pnpm test and lint the project with pnpm lint

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
Copy link

changeset-bot bot commented Aug 14, 2025

🦋 Changeset detected

Latest commit: ab5aeda

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
svelte Patch

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

Copy link
Contributor

Playground

pnpm add https://pkg.pr.new/svelte@16619

@Rich-Harris
Copy link
Member

Can we add a test for this?

@dummdidumm dummdidumm marked this pull request as draft August 15, 2025 21:42
@dummdidumm dummdidumm marked this pull request as ready for review August 17, 2025 20:13
@Rich-Harris
Copy link
Member

Rich-Harris commented Aug 18, 2025

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();
}

@dummdidumm
Copy link
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

@Rich-Harris
Copy link
Member

was just tinkering locally for my own curiosity (hadn't seen your reply), have a branch I can push up

@Rich-Harris
Copy link
Member

#16641

* use helper for async bodies

* unused

* fix

* failing test + fix

---------

Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>
@Rich-Harris Rich-Harris merged commit 1dcced5 into main Aug 18, 2025
16 checks passed
@Rich-Harris Rich-Harris deleted the catch-top-level-await-errors branch August 18, 2025 17:10
@github-actions github-actions bot mentioned this pull request Aug 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Redirects inside remote function queries not working as expected
2 participants