- From: Michael Cuneo <notifications@github.com>
- Date: Tue, 13 Apr 2021 00:24:39 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 13 April 2021 07:24:51 UTC
Well the old service worker was in a folder on an S3, the new service worker is in the root of a Lambda function, I push the site up using apex/up so I end up with a .zip in an S3 that is compiled into the lambda, and I don't really have any access or control over what gets into folders, how and when... some people who have seen or visited the site in the past, cannot see the new version so they're stuck. I can't do my usual old sw.js new sw.js workflow testing, because of the obvious, S3 <--> Lambda switch. Even if I injected some SSR sw.js code into the Lambda to serve, how do I know what folder it's in or where it's coming from. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1578#issuecomment-818507417
Received on Tuesday, 13 April 2021 07:24:51 UTC