[2.x] Fix <Deferred />
in Svelte adapter
#2037
Merged
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.
In issue #2012, the
<Deferred />
component was rendering its default slot before the necessary props were updated, leading to errors when accessing properties on undefined objects. To address this, I updated the<Deferred />
component to subscribe to the$page
store and usequeueMicrotask
skip a beat and switchloaded
when the props are expected to be updated.#2036 improves how
$page
is updated making it more predictable. The approach in this PR resolves the reactivity issue in the<Deferred />
component without modifying the$page
store, maintaining compatibility for existing projects.