Repository navigation
Publish browser starters that reuse the cached interface font - #56
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.
Refresh both downloadable browser projects from fullbleed-node#21, so documentation builds publish demos using the same versioned Inter font URL as the renderer. Chrome can then reuse the page's cached font response. The measured local saving is one 876,576-byte uncompressed font response per starter; Firefox and Playwright WebKit did not show that reduction.
The ZIPs contain the exact 14 browser-starter files and 17 React-starter files from merged source
bbb140f115a69ad77fc54bb9b5be2e908b7b6669. Every file is hashed in its source manifest. Both ZIPs were installed with fresh npm caches and built successfully, with copied runtime hashes checked. The strict site build and all 66 page/link/anchor checks passed. Upstream's 19 candidate checks passed, including all three browser engines, and the before/after invoice PDFs were byte-identical.The React guide's online-editor link uses the same merged source. A fresh anonymous import started the development app, loaded the versioned interface font, and downloaded the invoice with bytes matching the existing baseline.