Jeff Posnick

The upgrade flow for `workbox-precaching`—where you have an atomic set of previously cached URLs, and you migrate to a new set, with one or more of those cached URLs updated—relies...

We don't have any plans to change the `workbox-precaching` behavior to detach it from the service worker `install` and `activate` events. Those service worker events and the service worker lifecycle...

It wouldn't be called precaching. You can set up runtime caching routes to match whatever assets you want to be added to the cache, along the lines of what's described...

In general, I'd recommend serving your `service-worker.js` from the root of your web app, and registering it via ``` navigator.serviceWorker.register('/service-worker.js'); ``` I'm not sure why that wouldn't work for you—are...

This is similar to https://github.com/GoogleChrome/sw-precache/issues/39 I'd be curious to see what the pipeline and serving environment looks like. `sw-precache` makes some assumptions right now about what URL will be used...

I'm sympathetic to the `gulp`-pipeline use case for a production-y build. I'd suggest that using `sw-precache` in a webpack-dev-server environment is a bad idea anyway, since it will actively defeat...

That's the error you'd expect to see if you call `createHandlerBoundToURL('/index.html')` but there's no entry for `/index.html` in your precache manifest. Can you confirm that you're actually precaching `/index.html`?

I'm supportive of this change. As you mention, coming up with the right interface is a bit of a challenge. (This same challenge applies to other options that are currently...

FWIW, we still don't have a "native" way of doing `templatedURLs` in `workbox-webpack-plugin`, but there's a bit of a cleaner approach possible in v5, using a `ManifestTransform` function: https://github.com/GoogleChrome/workbox/issues/2398#issuecomment-597080778

A `manifestTransforms` function, when used in `workbox-webpack-plugin`, are passed a webpack `Compilation` object as the second parameter. This answer depends somewhat on exactly how your JS and CSS is being...