Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

use network-first strategy for start_url

See original GitHub issue

Since Lighthouse made it mandatory to respond to start_url when offline, we are pre-caching it (3.2.1). A build-time revision added by 3.3.0 / #386 but since revision is per-build, cached version for start_url may get stalled with target: 'server' since workbox does not supports NetworkFirst strategy for precache assets.

This is a known issue for users that use target: 'server':

If start_url is not customized or is distinct it might cache ATH version until next build
If start_url is customized to /, it might caching landing until next build

Issue Analytics

State:
Created 3 years ago
Reactions:12
Comments:5

Top GitHub Comments

7reactions

voxivoidcommented, Jan 19, 2021

any news regarding this issue? every time we do a new deploy the start_url gets stalled and then we get a lot of loading chunk errors because it tries to access files that do not exist anymore on the server

2reactions

niklaswolfcommented, Oct 8, 2021

Does anybody have a good workaround or ideas for this? This seems like a pretty major issue for users that install the app as PWA.

A real “bad” workaround could be to trigger a new build/deployment, when changes on the home-page are detected. This of course is highly dependent on where the content of this page is coming from. Of course this is not a solution to this problem and not an option for most people either…