fix: Reject all pending query promises when a query fails before resolving with a value for the first time - #16890
Merged
Merged
Conversation
…lving with a value for the first time
|
Install the latest version of pnpm add https://pkg.svelte.dev/@sveltejs/kit/c/61fb0156addb8666a86a883cb226b2c8878d8385Open in |
🦋 Changeset detectedLatest commit: 61fb015 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 |
Rich-Harris
approved these changes
Aug 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #16848
Failure Sequence
#readyisfalse.tick(), then returns#current.#currentisundefined.undefinedrather than a rejected promise, so<svelte:boundary>does not render its failure snippet. Accessing something likeresult.map(...)instead throws later.The same problem occurs when
fail()clears pending requests.Fix
If we see that the internal promise has resolved but
#readyhas not yet been set, reject with#error(or a fallback, which shouldn't ever be reached).