Skip to content

fix: prevent stale reads when tracking new dependencies during pending async work - #18674

Open
jkbz64 wants to merge 3 commits into
sveltejs:mainfrom
jkbz64:stale-reads
Open

fix: prevent stale reads when tracking new dependencies during pending async work#18674
jkbz64 wants to merge 3 commits into
sveltejs:mainfrom
jkbz64:stale-reads

Conversation

@jkbz64

@jkbz64 jkbz64 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Fixes sveltejs/kit#16207

I've found a minimal reproduction from the issue above and tried to slop it a bit, feel free to re-use the repro and fix it properly if it's bad.

Merges a newer batch with an earlier pending batch when it starts reading state changed by that batch, preventing stale values from reaching newly dependent UI.

The change also modified the behavior of some tests but the comments there said "if this is not here then this would also be ok" so I guess that passes? I'm not really confident about that change but it does not break other tests and seems to fix the issue.

Assisted-by: Codex

@pkg-svelte-dev

Copy link
Copy Markdown

Install the latest version of svelte from 0ec0b45:

pnpm add https://pkg.svelte.dev/svelte/c/0ec0b458fc80badcc2cfd78495abc23bfe9dc20d

Open in pkg.svelte.dev: https://pkg.svelte.dev/repos/svelte/pr/18674

Note

This PR is from a fork. A maintainer must approve approve each commit before it can be built and installed.

@changeset-bot

changeset-bot Bot commented Aug 19, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 0ec0b45

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

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.

Stale values when navigating from within a boundary

1 participant