I dropped it in a DM

Reply to this note

Please Login to reply.

Discussion

Ah, ok. See the issue. Other than livereload for some reason being in the production build (oops), looks like the service worker deregister implementation was naive. Many thanks, will patch it today.

hotfix will be deployed in roughly ~10 minutes. It's possible the error caused you to have breaking state. lmk if the error persists.

cleared cache, reloaded, and I see the same result. (btw, this is not urgent for me, just hoping to be helpful in debugging)

It might be a CDN caching issue, with the change that was added, it would be impossible for that error to occur.

CDN cache has been purged.

cleared cache and same results

Should have it this time. I'm assuming you're using Firefox in a private tab. It handles serviceWorkers in a secureContext, and I wasn't accounting for this case. ~10 minutes.

handles serviceWorkers in a secureContext differently*

Thanks for the help btw, it's difficult to rapidly develop + test every possible case in every possible browser :D

Well, I just figured it out. The changes weren't being deployed :D

that did it, working smoothly now