GoogleChrome / GoogleChrome/lighthouse

SW Audit: Verify that new index.html content will be fetched and served

Open
#2,147 1 comment 0 reactions 0 assignees View on GitHub
feature P3
Dominant language
JavaScript
Stars
30.8k
Forks
9.8k
Avg merge
1d 20h
Merged PRs (30d)
19

Description

@paulirish and I ran into this on caltrainschedule.io

While we thought our SW was operating correctly, it was always satisfied by the assets in the cache. As a result, it never went looking for a new asset from the network and the user only saw stale stuff.

The downsides of cache-first serving policy, I guess. :goat:

(issue authored by paul. thanks sam)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.