Workbox error logged to the console during report

[cyrilf]

Provide the steps to reproduce

1. Run LH on https://animal-kill-counter.luseeds.com/

What is the current behavior?

Under the "Best Practices" category I get a score of 93 because there is a "Browser errors were logged to the console".

URL	Description
https://cdn.jsdelivr.net/npm/workbox-cdn@4.3.1/workbox/workbox-strategies.prod.js	no-response: no-response :: [{"url":"https://animal-kill-counter.luseeds.com/"}] at a.makeRequest (https://cdn.jsdelivr.net/npm/workbox-cdn@4.3.1/workbox/workbox-strategies.prod.js:1:2145)

What is the expected behavior?

This error shouldn't occur.
It seems like it is not related to my website and comes only when a report is generated. 🤔

Environment Information

• Affected Channels: DevTools
• Lighthouse version: 5.7.0
• Chrome version: 81.0.4044.92 (Official Build) (64-bit)
• Node.js version: v13.9.0
• Operating System: Linux / Ubuntu

Related issues

[patrickhulce]

Thanks for filing @cyrilf! This is exactly the behavior I see in the console if I try to load your page with an empty cache and then try to visit the page again offline (which is what Lighthouse does). Your site uses workbox in its service worker, so it is coming from code you've referenced even if you're not the maintainer of workbox or nuxt :)

My guess is there's been a misconfiguration somewhere along the line with the offline cache strategy.

[cyrilf]

Thanks for the quick answer @patrickhulce
You're totally right, this seems to be a known issue with nuxt/workbox. For instance it's mentioned on this github issue.

Thanks and I close as it's not related to lighthouse! ✌️

[trevor-ofarrell]

@cyrilf did you ever find a way to solve this? I'm getting the same issues.

[cyrilf]

@trevor-ofarrell no I haven't checked in a while. But if you have a look at the github issue I've linked in my previous comment you might find some answers. 👍