Remix dev asset server web socket error

What version of Remix are you using?

1.4.1

Steps to Reproduce

1.npm i create-remix mydemo
2.remix dev
3.Modify or add files in routes
4.chrome error(Remix dev asset server web socket error:)

Expected Behavior

Automatically refresh the page to match the new route.
To fix this I had to reboot.

Actual Behavior

[Klukies]

Hey, I had the same issue.

Deleting my package-lock & node_modules however, fixed the issue for me. Hope this is the case for you as well!

Hey, I had the same issue.

Deleting my package-lock & node_modules however, fixed the issue for me. Hope this is the case for you as well!

#1601
Thanks, but your workaround didn't work for me. I found a similar question.

[TimoWestland]

Been having this issue as well since upgrading to v1.4.3. Re-installing dependencies did not work for me either.

[sillypoise]

Same bug has been happening to me as well since v1.4.3. Can reproduce the bug just as OP described.

[WesleyKapow]

So I believe the issue is that for some reason LiveReload is using a randomly generated port number when remix builds. For me, it'll work for a while but then when I introduce a compile bug and fix it, this triggers a new random number and I get a mismatch between the port actually being used and the one LiveReload is trying to connect to.

It looks like Remix is not respecting devServerPort, nor REMIX_DEV_SERVER_WS_PORT and not actually using the default port of 8002 as the docs outline.

My work around is to use <LiveReload port={8002}/>

[leimantas]

I have same problem.
Latest Safari. No extensions.
After reloading vscode - it works for some time.