Keep Trying to connect… after Disconnected

[nitin2953]

After terminating 11ty --serve, it keep Trying to connect… & logging into browser console

[11ty][12:07:39.465 UTC] Trying to connect…                  reload-client.js:21
[11ty][12:07:39.772 UTC] Connected                           reload-client.js:21

[11ty][12:08:40.546 UTC] Disconnected                        reload-client.js:21
[11ty][12:09:18.706 UTC] Trying to connect…                 reload-client.js:160
▼ WebSocket connection to 'ws://localhost:5555/' failed:     reload-client.js:21
    init @ reload-client.js:160
    reconnect @ reload-client.js:88

It should suppress WebSocket connection failed (? and Trying to connect… ?) warning
which will result:

(99) [11ty][12:09:18.706 UTC] Trying to connect…            reload-client.js:160

[zachleat]

Just as a quick note I believe it only attempts a reconnect on page focus or visibilitychange

[nitin2953]

Yes, it is only working on page focus AND visibilitychange

[zachleat]

Ah, sorry I think there has been a misunderstanding here? This is intentional behavior—we attempt to reconnect when you focus to the browser window.

If the server is down when you focus (or the tab’s visibility changes), it will report an error.

It doesn’t seem like this error is swallow-able via try catch, unfortunately. Some additional info here https://stackoverflow.com/questions/31002592/javascript-doesnt-catch-error-in-websocket-instantiation

If you’d like to request an option to this behavior, I can convert this one to be an enhancement request, though it feels like lower priority to me at the moment

[zachleat]

This is an automated message to let you know that a helpful response was posted to your issue and for the health of the repository issue tracker the issue will be closed. This is to help alleviate issues hanging open waiting for a response from the original poster.

If the response works to solve your problem—great! But if you’re still having problems, do not let the issue’s closing deter you if you have additional questions! Post another comment and we will reopen the issue. Thanks!

[zachleat]

Just one more small note here I did play around with adding an error handler to the websocket but that resulted in two errors in the console, which is not what we want 😅

[nitin2953]

If you’d like to request an option to this behavior, I can convert this one to be an enhancement request, though it feels like lower priority to me at the moment

I just want it to "Stop Reconnecting after Disconnection"