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
After building in paths we get like href="/favicon.ico" or href="/static/css/main.894a7f1d.chunk.css" and for proper working and for deplyoing it need to be changed in href="./favicon.ico" and href="./static/css/main.894a7f1d.chunk.css". And also i found that many people get the error( Failed to load resource: the server responded with a status of 404 ()) after deploying their apps, for example, on github pages, and get white blank. Because path are wrong.
The text was updated successfully, but these errors were encountered:
One way to solve this is to keep the existing files available for some time after deployment of a new version, but also look into ways to invalidate the existing HTML file - perhaps there's an aggressive CDN in the way?
You could also look at tweaking your service worker. There are a few discussions on this topic available, such as GoogleChromeLabs/sw-precache#356.
After building in paths we get like href="/favicon.ico" or href="/static/css/main.894a7f1d.chunk.css" and for proper working and for deplyoing it need to be changed in href="./favicon.ico" and href="./static/css/main.894a7f1d.chunk.css". And also i found that many people get the error( Failed to load resource: the server responded with a status of 404 ()) after deploying their apps, for example, on github pages, and get white blank. Because path are wrong.
The text was updated successfully, but these errors were encountered: