You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 404 errors get annoying in the console. Not quite sure what the benefit of including it service-worker.js is. We could do a debug exclude, or not include it on the hard list, or router around it.
I don't see much benefit to having main.md5hash.css in precache... it's already on the html by the time the sw runs. Or perhaps it would be better to do a quick prod cleanup before running in dev mode.
thoughts?
UPDATE: Sample error:
/service-worker.js:132 Request for http://localhost:8000/styles/main.7af9a142.css?sw-precache=1473853567887 returned a response with status 404, so not attempting to cache it.
The text was updated successfully, but these errors were encountered:
FossPrime
changed the title
sw tries to load production css due to precache
sw tries to load prod css in dev due to precache
Sep 12, 2016
FossPrime
changed the title
sw tries to load prod css in dev due to precache
Service Worker configured to load "prod" styles on "dev" results in 404
Sep 14, 2016
The 404 errors get annoying in the console. Not quite sure what the benefit of including it service-worker.js is. We could do a debug exclude, or not include it on the hard list, or router around it.
I don't see much benefit to having main.md5hash.css in precache... it's already on the html by the time the sw runs. Or perhaps it would be better to do a quick prod cleanup before running in dev mode.
thoughts?
UPDATE: Sample error:
The text was updated successfully, but these errors were encountered: