The service worker is a web API that helps you cache your assets and other files so that when the user is offline or on slow network, he/she can still see results on the screen, as such, it helps you build a better user experience, that’s what you should know about service worker’s for now. … Read more
Update Jan 15 2018 The StorageManager interface of Storage API is becoming a standard for all storage related api queries. As mentioned by @miguel-lattuada, the estimate API would provide an estimate of the storage used a web app the available storage. Also, note the QuotaExceededError exception which would help us in handling error scenarios. eg … Read more
I wanted to expand on some of the other answers here, and approach this from the point of view of “what strategies can I use when rolling out a service worker to production to ensure that I can make any needed changes”? Those changes might include fixing any minor bugs that you discover in production, … Read more
Disabling ETag header from backend solved this issue temporarily.
As an alternative to using self-signed certificates, you can launch Chrome or Firefox such that it pretends certain domains are secure. For example, using Chrome on a Mac, you can launch it using: /Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ –user-data-dir=/tmp/foo –unsafely-treat-insecure-origin-as-secure=http://www.your.site Service workers should then work from http://www.your.site. More info can be found here: Options for testing … Read more
Access to Opaque Responses’ Headers / Body The most straightforward limitation around opaque responses is that you cannot get meaningful information back from most of the properties of the Response class, like headers, or call the various methods that make up the Body interface, like json() or text(). This is in keeping with the black-box … Read more
No cache scenario (No Service worker): Your PWA app will be cached only when you use Service worker. Manifest.json will help adding your web app to home screen with a icon and open without address bar. If you don’t have a service worker or if your browser don’t support it, web page will be loaded … Read more
You may not need a service worker for your application. If you are creating a project with create-react-app it is invoked by default Service workers are well explained in this article. To Summarise from it A service worker is a script that your browser runs in the background, separate from a web page, opening the … Read more
In general, you need to serve both your page and your service worker script via HTTPS in order to use service workers. The rationale is described at Prefer Secure Origins For Powerful New Features. There’s an exception to the HTTPS requirement in place to facilitate local development: if you access your page and service worker … Read more
Buksy’s answer is correct but in my opinion it does not answer the original question, namely: “What can service workers do that web workers cannot? Or vice versa?” There are fundamental differences in their lifecycle and the number of instances per origin you can have. In short: | Web Workers | Service Workers | |————–|————–|——————| … Read more