Is it ok to use Workbox's `injectManifest` with the recent recipes `warmCache` option?

I tried this without success in the Service Worker in Pack11ty:

```javascript
staticResourceCache({
warmCache: self.__WB_MANIFEST,
});
```

Other caches are warmed up, not this one.

#ServiceWorker #Workbox

⚓️ https://nicolas-hoizey.com/notes/2023/05/06/1/

Note from 6 May 2023

Is it ok to use Workbox's `injectManifest` with the recent recipes `warmCache` option? I tried this without success in the Service Worker in Pack11ty…

Nicolas Hoizey

You can try youself: go to https://pack11ty.dev with an empty Cache storage, wait for the Service Worker installation and caches warm up.

There will be:
- `workbox-offline-fallbacks`
- `pages`
- `images`

But not `static-resources` until a page refresh… 🤷‍♂️

(And no error in the console.)

Ping @jeffposnick maybe?

Pack11ty, an heavily opinionated Eleventy template project

Pack11ty is an heavily opinionated Eleventy template project created by Nicolas Hoizey.

Pack11ty

@tomayac thanks Thomas 🙏

@jeffposnick @tropicadri I can open an issue on GitHub, if necessary.

@tomayac @jeffposnick @tropicadri Ok, I didn't find any way to fix my bug, so I created an issue on GitHub: https://github.com/GoogleChrome/workbox/issues/3207
Issue with `warmCache` option in `staticResourceCache` recipe · Issue #3207 · GoogleChrome/workbox

Library Affected: workbox-cli 6.5.4 (using injectManifest) and workbox-recipes 6.5.4 Browser & Platform: At least Chrome stable, couldn't replicate in Firefox where devtools are less powerful for s...

GitHub