or <meta> tags as // strings inside this file. Crawlers (Facebook, // WhatsApp, regex-based scrapers) can latch onto the // first <title>...

if ('serviceWorker' in navigator) { window.addEventListener('load', function() { navigator.serviceWorker.register('/sw.js').catch(function() {}); }); } // ChunkLoadError recovery. Two real-world triggers: // • Dev: Webpack/Turbopack rebuilds mid-navigation, a Link // prefetch hits a chunk URL that 404s for ~1s. The 404 // comes back as text/plain HTML, browser refuses MIME // → ChunkLoadError. // • Prod: the SW cached an older /page HTML referencing // content-hashed chunks the new deploy purged. A plain // reload doesn't help because the SW serves the stale // shell again. // // Strategy: // 1st hit → unregister SWs + clear all caches, then reload. // The SW step is what makes prod actually recover. // 2nd hit → reload once more (Fast Refresh / SW activation // sometimes needs a second pass). // 3rd hit → replace the document with an actionable // "app updated" panel so the user isn't stuck // on the bare Next.js overlay with no context. // // Listeners run in the capture phase so we beat Next's dev // error overlay to the event and suppress the flash. (function() { function isChunkLoadError(err) { var msg = (err && (err.message || String(err))) || ''; var name = err && err.name; if (name === 'ChunkLoadError') return true; return /ChunkLoadError|Loading chunk .+ failed|Failed to load chunk|Refused to execute script.+MIME/i.test(msg); } function clearClientState(cb) { var done = false; var finish = function() { if (!done) { done = true; cb(); } }; // Hard cap so a stuck SW unregister can't hang the reload. setTimeout(finish, 1500); try { var swP = ('serviceWorker' in navigator) ? navigator.serviceWorker.getRegistrations().then(function(regs) { return Promise.all(regs.map(function(r) { return r.unregister().catch(function(){}); })); }).catch(function(){}) : Promise.resolve(); var cacheP = (typeof caches !== 'undefined' && caches.keys) ? caches.keys().then(function(keys) { return Promise.all(keys.map(function(k) { return caches.delete(k).catch(function(){}); })); }).catch(function(){}) : Promise.resolve(); Promise.all([swP, cacheP]).then(finish, finish); } catch (e) { finish(); } } function showRefreshPanel() { try { // IMPORTANT: never serialize or <meta> tags as // strings inside this file. Crawlers (Facebook, // WhatsApp, regex-based scrapers) can latch onto the // first <title>... they find anywhere in the // document source — including inside a

Forgot password?