Issues after deployment of PWA

Questions
1

Hello there,
After deployment of the production code (f7 version &) I am getting the following error:
TypeError: ls.on is not a function

[…]
ls.mount(“#app”);
window.history.pushState(null, null, window.location.href);
window.onpopstate = function() {
window.history.go(1)
}
;
ls.on(“init”, e=>{ <<< error location
var t = globalThis;
t.firstStart = !0
}
);
[…]

the WPA link is here: https://nyc.silverball.city/
a workng npm instance is available here: http://pinapp.groobo.com:3002/
Does anyone know what could be wrong and where to start looking?
Thanks in advance for your help!

2

This error seems to be blocking any updates. I am loosing my mind trying to force the ‘old’ page 1.4.3 to go to ‘new’ 2.1.5. You probably never see the 1.4.3 because it’s your first time, but I cannot get rid of it. I tried http redirects to domain.com?v=2 but even those did not kick in. How can I force the ‘OLD’ code to give up loading from cache and go get the newest content? Not a PWA expert, Thanks

3

Usually, the browser checks for service worker updates automatically, that is any changes made to the service-worker.js file. When it finds a change, it loads the new one and starts using it on the next page load. On your machine you can always refresh everything using the Dev Tools in your browser.
Try making sure you update your service worker with the updated assets and then deploy it again.
Hope to be helpful!

4

Try adding “npm version patch” in your package.json.
Example:

“scripts”: {
“build”: “npm version patch & cross-env NODE_ENV=production vite build”,
},

Somewhere in your application (i use in logout button):
if (‘serviceWorker’ in navigator) {
navigator.serviceWorker
.getRegistrations()
.then(function (registrations) {
for (let registration of registrations) {
registration.unregister()
}
})
}