fix(i18n): key the catalog's cache by its content, not the release

The service worker serves the locale catalog's boot script cache-first,
and its URL carried the package version. Every build of one release
therefore shared one URL: an instance updated within a release (a beta,
a redeploy) kept the catalog of its first build, and every message added
since read as its raw key ("timeline.zoom.range", "timeline.selection.week")
or fell back to English.

next.config.ts now hashes the message catalogs at build time and the
layout keys the script by that hash, so a changed catalog is a new URL.
This commit is contained in:
Marc-André Bombeck committed 2026-10-09 13:13:26 +02:00
1 parent cd78415084
commit 3f47224825
5 files changed
+63 -3

No files matched your search

+3 -1
View File
@@ -131,7 +131,9 @@ export default async function RootLayout({
id="healthlog-i18n-boot"
strategy="beforeInteractive"
nonce={nonce}
src={`/i18n/${initialLocale}.js?v=${process.env.NEXT_PUBLIC_APP_VERSION || "dev"}`}
// Keyed by the catalogs' content (`next.config.ts`), not the
// release: the service worker serves this URL cache-first.
src={`/i18n/${initialLocale}.js?v=${process.env.NEXT_PUBLIC_I18N_CATALOG_VERSION || "dev"}`}
/>
</head>
<body className={`${inter.variable} font-sans antialiased`}>