Repository navigation
fix(router): reuse SSR-rendered loader data when the first fetch eTag matches - #9221
Merged
Merged
Conversation
… matches Loaders with serializationStrategy 'never' fetch their data on the first client read, which reran every subscriber even when the data was unchanged. When the loader has an eTag option, SSR now stores the same eTag the q-loader endpoint sends, and a matching first fetch adopts the value without notifying.
🦋 Changeset detectedLatest commit: d73c60a The changes in this PR will be included in the next version bump. This PR includes changesets to release 8 packages
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 |
@qwik.dev/core
@qwik.dev/router
@qwik.dev/utils
eslint-plugin-qwik
create-qwik
@qwik.dev/optimizer
@qwik.dev/devtools
@qwik.dev/mcp
commit: |
Contributor
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
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.
Loaders with serializationStrategy 'never' fetch their data on the first client read, which reran every subscriber even when the data was unchanged. When the loader has an eTag option, SSR now stores the same eTag the q-loader endpoint sends, and a matching first fetch adopts the value without notifying.