Repository navigation
Add CSS cache keys across build, publish, and serve. - #18
Merged
Merged
Conversation
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
1 participant
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.
Summary
Add CSS cache keys across build, publish, and serve
Changes
Generated stylesheets now use keyed filenames such as
site.<key>.cssandsite.<key>.dark.css, with matching HTML links. This prevents browsers and hosts from reusing stale CSS after a new deployment.Build and publish generate a fresh key per full build. Serve uses one key per session and retains its existing
no-storeresponses for edits. Keys stay outside the resolved configuration so manifest reuse continues to work. Custom paths, query strings, fragments, and base paths are preserved.Validation
All 477 tests passed, along with TypeScript and lint checks. Added coverage for keyed theme URLs and matching files and page links in build and publish.