From 085d996dbe7a3fa089baab1ea40cf16280d0be83 Mon Sep 17 00:00:00 2001 From: Naveed Ahmed Date: Tue, 7 Sep 2021 21:29:44 +0500 Subject: [PATCH] docs(service-worker): update SW guide to include changes about cache removal update safety worker section in service worker guide and mention that safety worker also removes the SW caches --- aio/content/guide/service-worker-devops.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/aio/content/guide/service-worker-devops.md b/aio/content/guide/service-worker-devops.md index d9f5d73968f56..cb3982531bc06 100644 --- a/aio/content/guide/service-worker-devops.md +++ b/aio/content/guide/service-worker-devops.md @@ -326,8 +326,9 @@ essentially self-destructing. Also included in the `@angular/service-worker` NPM package is a small script `safety-worker.js`, which when loaded will unregister itself -from the browser. This script can be used as a last resort to get rid -of unwanted service workers already installed on client pages. +from the browser and remove the service worker cache. This script can +be used as a last resort to get rid of unwanted service workers already +installed on client pages. It's important to note that you cannot register this worker directly, as old clients with cached state may not see a new `index.html` which @@ -340,7 +341,7 @@ old Service Worker URL forever. This script can be used both to deactivate `@angular/service-worker` as well as any other Service Workers which might have been served in -the past on your site. +the past on your site along with the corresponding caches. ### Changing your app's location