Skip to content

fix: allow async {@const} in more places #16643

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 1 commit into from
Aug 22, 2025
Merged

fix: allow async {@const} in more places #16643

merged 1 commit into from
Aug 22, 2025

Conversation

dummdidumm
Copy link
Member

@dummdidumm dummdidumm commented Aug 18, 2025

Implemented by reusing the async_body function inside Fragment.js. Also removes the ability to reference a {@const ...} of an implicit child inside a boundary pending/failed snippet:

  • existing duplication of consts can have unintended side effects, e.g. async consts would unexpectedly called multiple times
  • what if a const is the reason for the failure of a boundary, but is then referenced in the failed snippet?
  • what if an async const is referenced in a pending snippet? deadlock
  • inconsistent with how it behaves for components where this already does not work

Implemented via / only taking effect with the experimental flag so the behavior change only applies there as this is a breaking change strictly speaking. Also added a compiler error for this.

closes #16462

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 Aug 18, 2025

🦋 Changeset detected

Latest commit: d41d821

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

@svelte-docs-bot
Copy link

Copy link
Contributor

Playground

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

Implemented by reusing the `async_body` function inside `Fragment.js`. Also removes the ability to reference a `{@const ...}` of an implicit child inside a boundary pending/failed snippet:
- existing duplication of consts can have unintended side effects, e.g. async consts would unexpectedly called multiple times
- what if a const is the reason for the failure of a boundary, but is then referenced in the failed snippet?
- what if an async const is referenced in a pending snippet? deadlock
- inconsistent with how it behaves for components where this already does not work

Implemented via the experimental flag so the behavior change only applies there as this is a breaking change strictly speaking. Also added a compiler error for this.

closes #16462
@philipplentzen
Copy link

I had the same issue, and this PR fixed it for me.

@philipplentzen
Copy link

As in #16571, the value of $effect.pending() is stuck at a non-zero value after the initial promise has been resolved. For subsequent promises inside the boundary the counter works fine. Is this the intended behavior?

See Playground

@Ocean-OS Ocean-OS merged commit a60995a into main Aug 22, 2025
16 checks passed
@Ocean-OS Ocean-OS deleted the async-const-blocks branch August 22, 2025 17:28
@github-actions github-actions bot mentioned this pull request Aug 18, 2025
@dummdidumm
Copy link
Member Author

@philipplentzen can you open an issue for this? thanks

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.

await doesn't work with @const
3 participants