Fix SW issues

Author: ThatHackerDudeFromCyberspace

assets/js/global.js

@@ -0,0 +1,20 @@
+const registerServiceWorker = async () => {
+    if ("serviceWorker" in navigator) {
+        try {
+            const registration = await navigator.serviceWorker.register("/service_worker.js", {
+                scope: "/",
+            });
+            if (registration.installing) {
+                console.log("Service worker installing");
+            } else if (registration.waiting) {
+                console.log("Service worker installed");
+            } else if (registration.active) {
+                console.log("Service worker active");
+            }
+        } catch (error) {
+            console.error(`Registration failed with ${error}`);
+        }
+    }
+};
+
+registerServiceWorker();

service_worker.js

@@ -0,0 +1,22 @@
+// sw.js
+
+self.addEventListener('install', () => {
+    // Skip over the "waiting" lifecycle state, to ensure that our
+    // new service worker is activated immediately, even if there's
+    // another tab open controlled by our older service worker code.
+    self.skipWaiting();
+  });
+  
+  self.addEventListener('activate', () => {
+    // Optional: Get a list of all the current open windows/tabs under
+    // our service worker's control, and force them to reload.
+    // This can "unbreak" any open windows/tabs as soon as the new
+    // service worker activates, rather than users having to manually reload.
+    self.clients.matchAll({
+      type: 'window'
+    }).then(windowClients => {
+      windowClients.forEach((windowClient) => {
+        windowClient.navigate(windowClient.url);
+      });
+    });
+  });