Skip to content

Conversation

Rich-Harris
Copy link
Member

@Rich-Harris Rich-Harris commented Sep 29, 2025

This is part of a project to update some of the async batching logic to handle a few edge cases that have cropped up.

The observable change here is that if you have an await expression that runs twice, and the second one somehow resolves before the first, they are no longer forced to resolve in linear order. The easiest way to see it is in this example — click a++ then b++ in quick succession:

  • main — the fast b++ update is blocked on the slow a++ update
  • this PR — the b++ update occurs, followed by the a++ update

To make this work, whenever a batch is committed, we essentially 'rebase' other pending batches on top of the newly applied state. In the example above, when we commit the fast b++ update, we re-run any async effects that depend on b in the context of the pending a++ batch.

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

changeset-bot bot commented Sep 29, 2025

🦋 Changeset detected

Latest commit: a50d0ec

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@16866 
@Rich-Harris
Copy link
Member Author

moving back to draft, some more improvements incoming

@Rich-Harris Rich-Harris marked this pull request as draft September 29, 2025 20:45
@Rich-Harris Rich-Harris marked this pull request as ready for review September 29, 2025 20:50
@Rich-Harris
Copy link
Member Author

In addition to the tests that are updated in the PR, this fixes the async-redirect test which, for reasons I don't begin to understand, passes on main despite being completely broken. Press 'b', then 'ok', then 'b' again and observe the difference in behaviour:

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks awesome. I'll wait for Simon to review as well before approving; I think everything is good but given he's more familiar with the clientside stuff he should definitely take a look

Comment on lines -18 to -27
// TODO why is this necessary? why isn't `await tick()` enough?
await Promise.resolve();
await Promise.resolve();
await Promise.resolve();
await Promise.resolve();
await Promise.resolve();
await Promise.resolve();
await Promise.resolve();
await Promise.resolve();
flushSync();

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😆 I saw this while I was working on async SSR and I was really hopeful we could murder it at some point

Copy link
Member

@dummdidumm dummdidumm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice one!

@dummdidumm dummdidumm merged commit 25cbdc8 into main Sep 30, 2025
18 checks passed
@dummdidumm dummdidumm deleted the merge-batches branch September 30, 2025 13:57
@github-actions github-actions bot mentioned this pull request Sep 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants