workbox | 📦 Workbox: JavaScript libraries for Progressive Web Apps | Command Line Interface library

So for my ReactJs project, I am using absolute path for import, like this import {button} from /buttons

instead of relative path like this: import {button} from ../../buttons

It works fine for npm start, but when I try to build with npm run build I get the following error:

I am currently using the workbox-build module, specifically the generateSW mode, to generate my service worker scripts to deploy my web application to Netlify. My site is a static site.

Here is my worker-config.js:

I have a web application that wants to cache recently-referenced images to support offline use. The images are not expected to ever change, so I have configured my Workbox-based service worker to use the CacheFirst strategy for all requests from the image server:

After upgrading my webpack from v4 to v5, I got this error that is getting me a hard time debugging.

I have a TypeScript-based Vuejs project compiled and bundled using Vite.

I am trying to configure the build system to compile my custom service worker (src/service-worker.ts) and place the output in dist/service-worker.js. In particular, I don't want it included as part of the application's JS bundle, because it needs to be served at that well-known URL as part of a static website.

The existing structure is like:

After upgrading react-scripts to v5, craco start does not work properly. App starts with no error but in browser, there is a blank page and if i open inspector, i only see index.html codes not react codes. It was working well with react-scripts@4.0.3. Here is my local files;

package.json

I'm trying to let user know that the app is updated after installing the new service worker. But the problem is after doing the typical skipWaiting() and ClientsClaim() and trying to send message to clients that there is an update, clients array is empty.

index.js

I'm new to SvelteKit and trying to find out how to load the Google client library for Javascript.

Google tells me to do it like this:

We have developed a PWA to provide a subset of functionality to our users while offline. We use IndexedDB and Workbox 6.2.0 to cache data, static assets and API calls and serve them to the user via a service worker while offline.

It works really well on Android; but on iOS, it intermittently displays the "Safari cannot open the page" native error page instead of the offline functionality. On iOS 14 restarting the device fixes it, and all cached data is still there. On iOS 15 we don't need to restart the device: Usually killing all tabs and Safari does the trick and the PWA is available offline again; sometimes it won't work until we go back online; other times it comes back to life just by leaving it alone.

Tethering the device and debugging the PWA with Safari or Chrome DevTools doesn't show anything when the PWA errors - It doesn't show any registered service worker, cache, or DB.

• There is a offline fallback page configured to be shown if the user tries to reach a resource that hasn't been cached, so this question doesn't apply.
• Unlike this question, the PWA comes back to life if we connect back to the Internet, and then it works offline again.
• This question suggests the device could be low on free storage, but ours has 6GB of storage left.
• We're aware there's a bug in iOS 14 that's consistent with what we've seeing, but it should be fixed in iOS 15.
• We also know there was a bug with importScripts that meant Workbox wasn't cached properly, but that should be fixed now too (we use importScripts to pull Workbox from Google's CDN)

To be honest, I've ran out of ideas about how to get this diagnosed, let alone fixed. Has anybody come across this before, or can suggest a way of getting some diagnostics data?