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
Try to open another page running in a different sub-folder
Expected Behavior
The current service worker file (serviceWorker.js) doesn't addresses the case when the app is server from a sub route, it should make sure to cache and serve assets only on the PUBLIC_PATH route.
Actual Behavior
The service worker will try to cache and serve all the domain assets.
Reproducible Demo
No demo needed I guess. (and anyway I'm not sure how to provide one actually)
The text was updated successfully, but these errors were encountered:
I'm not sure what action to take here—the service worker, as it's currently set up, will precache everything that's included in the webpack build by default. Changing that to a different behavior would be a fairly significant breaking change for folks who do choose to use the generated service worker.
That being said, this should be viewed in the context of #3924 and the related to change to make service worker usage opt-in. Folks who don't want the precaching behavior will presumably not opt-in.
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 7 days if no further activity occurs.
Is this a bug report?
yes
Did you try recovering your dependencies?
Not related
Which terms did you search for in User Guide?
service worker
Steps to Reproduce
(Write your steps here:)
homepage
to a sub-folder in package.jsonExpected Behavior
The current service worker file (serviceWorker.js) doesn't addresses the case when the app is server from a sub route, it should make sure to cache and serve assets only on the PUBLIC_PATH route.
Actual Behavior
The service worker will try to cache and serve all the domain assets.
Reproducible Demo
No demo needed I guess. (and anyway I'm not sure how to provide one actually)
The text was updated successfully, but these errors were encountered: