Closed liamhart96 closed 3 years ago
Hi ๐,
no issues here, can you provide some additional info?
Hi
Node v14.16.1 Chrome Mac OS 11.3.1
Hi ๐,
I just set up an environment equivalent to the info you provided. Everything seems to work, including reloader.
I could reproduce the error message only after I stopped the npm run start
task in the terminal.
I think what you are encountering is actually expected behavior. By running npm run start
it spins up a WebSocket server which is required for remote reloading. If the server isn't running you'll get the error, since the remote script tries to establish a connection to the server every couple of seconds.
Hi, i have the same issue, any news ??
Node v15.6.0 Chrome Windows 10 Insider Preview 21376.1
I just tried it out in a couple of different environments, and I can't reproduce the issue. For me, reloader works everywhere.
The above-mentioned error basically tells that the reloader client script (on the remote Shopify store) which is injected into the webpack bundle can't connect to the dev server (which is started by running the start
task).
So I'm assuming if the reloader functionality isn't working for somebody it's because something is blocking the WebSocket connection on their system. Especially if there are no errors being thrown in the terminal after running npm run start
reloader
in package.json
and restart the start
taskThe problem has suddenly vanished, I don't have any problem with reloading, it's strange but everything works now ๐
Reloader seems to have an issue, it says disconnected.
ERROR in console:-
WebSocket connection to 'ws://localhost:5050/' failed: _init @ client.js:21 eval @ client.js:39