Add branding hash for PWA/static assets and improve caching behavior #983
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.
Use a
VITE_BRANDING_HASHderived from thebranding/folder to version all branding-related assets (favicon, manifest, PWA icons, screenshots, OG image, logos), so branding changes are visible immediately without manual hard reloads.Changes
getBrandingHash(brandingDir)and computeVITE_BRANDING_HASHinvite.config.ts.%VITE_BRANDING_HASH%(HTML)import.meta.env.VITE_BRANDING_HASH(TS/JS/plugins)index.htmlto append?v=%VITE_BRANDING_HASH%to:/favicon.ico/icons/apple-touch-icon.png/manifest.jsonBrandingManifestPlugin+ manifest generation:?v=VITE_BRANDING_HASHto manifesticons[].srcandscreenshots[].src.?v=VITE_BRANDING_HASHtoBRANDING_LOGO_LIGHT/BRANDING_LOGO_DARKenv values.precacheAndRoute(self.__WB_MANIFEST)(no manual favicon/manifest entries).activate, callcleanupOutdatedCaches(), delete theimagesruntime cache, claim clients, and reload them.