progressive-web-apps

I was following this article here (which is not complete unfortunately) in attempt to learn how to friend Ionic 3 based PWA and Firebase Cloud Messaging: Push Notifications with FCM What I did: as advised in the article added FCM libraries into service-worker.js: 'use strict'; importScripts('./build/sw-toolbox.js'); importScripts('https://www.gstatic.com/firebasejs/4.9.0/firebase-app.js'); importScripts('https://www.gstatic.com/firebasejs/4.9.0/firebase-messaging'); firebase.initializeApp({ // get this from Firebase console, Cloud messaging section 'messagingSenderId': '47286327412' }); const

In app.js , I am checking the serviceWorker existence in navigator object and if available then registering the SW. if ('serviceWorker' in navigator) { navigator.serviceWorker.register('./service-worker.js', { scope: './' }) .then(function(registration) { console.log("Service Worker Registered!"); }).catch(function(err) { console.log("Service Worker not registered!", err); }); } When trying to register SW, I receive the below error in Firefox. I also made sure the service-worker.js file is under src directory. Checking my about:config in Firefox (version 59.0.2) I had service worker and

I know there are some similar questions like so unexpected token after angular 2 production build but it doesnt actually answer my question. Basically I have an angular app and its a PWA, now everytime I do a new production build the first time I visit the site I get an error like so and then as soon as I refresh the page, the site works as normal. This happens on any browser/device Now my suspicion is that every time the app is updated, the main bundled js file changes, and the PWA has cached the old one and the app is still trying to use the new one. My Project structure is as follows I have

I have a SSR Angular app which I am trying to transform into a PWA. I want it to be server-side rendered for SEO and for the "fast first rendering" that it provides. The PWA mode works fine when combined with SSR, but once the app is loaded, when we refresh it, the client index HTML file is loaded instead of the server-side rendered page. I have dug into the code of ngsw-worker.js and I saw this: // Next, check if this is a navigation request for a route. Detect circular // navigations by checking if the request URL is the same as the index URL. if (req.url !== this.manifest.index && this