JSONP errors when new bundle available (ServiceWorker)

[freecodecamp]

JSONP errors when new bundle available (ServiceWorker)

[raisedadead]

That is fine, it could be a caching issue. And a refresh should actually fix it. I don't know if we have a clean way to let this be known to users.

[raisedadead]

We use, Gatsby there is a service worker there already.

[Bouncey]

There is a service worker, and it does require a refresh with the bundles update. I would welcome any improvement on this, or the removal is none is found.

[Greenheart]

Good point, the caching idea is potentially the problem - I had recently visited learn.freecodecamp.org from that browser.

In other browsers that loaded the new version, it worked fine.

I imagine a ServiceWorker, that could take control of the cache would be ideal to solve this without involving our users. It could work in the background to keep data offline as well as caching the main application bundle - and resolving issues like this one

"Service workers essentially act as proxy servers that sit between web applications, the browser, and the network (when available)."
https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API

[Greenheart]

Perhaps it could intercept the request for the new bundle version as well?
Or rather, if network is present, force-update to use the latest bundle.

[Greenheart]

It happened again. Pretty sure this is a caching error, when the outdated service worker tries to fetch the old bundle that no longer exists.

And without any bundle to start the Learn-app, nothing happens once the button is clicked.

Since this occurred again now that I tried a new version than last time, I suspect this will happen if I try again once another update is released.

To fix this, could the service worker be updated to always request the latest bundle, rather than an outdated (seemingly hard coded) version that no longer exists on the server?

[Bouncey]

Service worker has been removed 👍