If I open a fragment URL (/#foo) while offline, I get an error page rather than a response from the service worker, even though the base URL (/) works fine offline.
Our workaround has been to pass fallbacks: { document: "/" } as an option.
I just wanted to check if this is intended behavior at all?
Summary
If I open a fragment URL (
/#foo
) while offline, I get an error page rather than a response from the service worker, even though the base URL (/
) works fine offline.Our workaround has been to pass
fallbacks: { document: "/" }
as an option.I just wanted to check if this is intended behavior at all?
(I found a related old issue on workbox that might be of interest: https://github.com/GoogleChrome/workbox/issues/488)
Configuration
Versions
next-pwa
: 5.6.0next
: 13.0.4