Next.js PWA: service worker never registers (getRegistration() undefined) and Playwright offline reload fails with net::ERR_INTERNET_DISCONNECTED: window 'load' fired before useEffect
Symptom: a Next.js 14 App Router dashboard shipped public/sw.js (cache-first for static assets, cached snapshot of API data) and a client component in the root layout to register it. A Playwright check then reported: - await navigator.serviceWorker.getRegistration() -> undefined ("Service Worker registered: false"), even 2 s after the page rendered - await context.setOffline(true); await page.reload(); -> Error: page.reload: net::ERR_INTERNET_DISCONNECTED
The registration component:
'use client'; export function ServiceWorkerRegister() { useEffect(() => { if ('serviceWorker' in navigator) { window.addEventListener('load', () => { navigator.serviceWorker.register('/sw.js'); }); } }, []); return null; }
Cause (likely): the window.addEventListener('load', ...) pattern is copied from plain-HTML PWA guides. In React/Next.js the effect runs after hydration, and on a fast page the load event has usually already fired by then, so the listener never runs and nothing is registered. No error is logged because register() is never called. Without a registered, controlling worker, an offline reload goes straight to the network and Chromium shows its offline error page; Playwright surfaces that as net::ERR_INTERNET_DISCONNECTED from page.reload().
Fix: register immediately when the document has already loaded:
useEffect(() => { if (!('serviceWorker' in navigator)) return; const register = () => navigator.serviceWorker.register('/sw.js').catch(console.error); if (document.readyState === 'complete') register(); else window.addEventListener('load', register, { once: true }); }, []);
Test it properly in Playwright: 1. page.goto('/') and wait for the worker to control the page: await page.waitForFunction(() => navigator.serviceWorker.controller !== null) (sw.js should call self.clients.claim() in activate, or you need one extra reload). 2. Only then context.setOffline(true) and page.reload(). 3. Expect the cached shell. API calls (for example a Server-Sent Events stream) will still fail offline; render the cached snapshot instead.
Also check: the worker has to be served from the site root (/sw.js) for scope '/', and registration requires a secure context; http://localhost and http://127.0.0.1 count as secure, a LAN IP over http does not.