Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Firefox page-refresh-on-save doesn't work

See original GitHub issue

Hello! In playing with Fresh, I’ve found that the websocket connection fails in Firefox (Developer Edition, 105.0b6 (64-bit)) and that means that refresh-on-save doesn’t work. Both Chrome and Safari work on the same machine.

The console error says:

The connection to http://localhost:8000/_frsh/alive was interrupted while the page was loading. [refresh.js:1:79](http://localhost:8000/_frsh/refresh.js)

I tested this on a new install of Fresh, doing

deno run -A -r https://fresh.deno.dev my-project
Selecting n for tailwind, and y for VSCode
Running deno task start

Issue Analytics

State:
Created a year ago
Reactions:7
Comments:9 (3 by maintainers)

Top GitHub Comments

4reactions

xxSkyycommented, Oct 29, 2022

I’ve got kinda temporary fix for it, for me it works great at least. in static folder add this file:

static/reloader.js

new EventSource("/_frsh/alive").addEventListener("error", (_err) => {
  setInterval(async () => {
    const response = await fetch("/_frsh/alive")

    if (response.status === 200) location.reload()
  }, 100)
})

then add this script it to your routes/_app.tsx (or create new one like mine, it’s like index.html in Vite)

import { Head, asset } from "$fresh/runtime.ts"
import { AppProps } from "$fresh/server.ts"

export default function App(props: AppProps) {
  return (
    <>
      <Head>
        <script src={asset('/reloader.js')} />
      </Head>
      <props.Component />
    </>
  )
}

It’s just detecting error caused by restart and then reload page when it’s available again, so overall same experience and even reload pages on manual restart. One cons is flooded console with failed requests if restart takes longer.

4reactions

lucacasonatocommented, Sep 6, 2022

Following FF bug is likely to be blamed: https://bugzilla.mozilla.org/show_bug.cgi?id=1706003. Firefox is not properly reconnecting EventSource on lost connection.