Closed Asher978 closed 5 years ago
@Asher978 I think this issue come from websocket, it has a route use('/ws') in server.js and api.js. You should check these files to make sure that websocket works well or maybe remove all them if you don't use websocket
@goodguy000 i will be using websockets.
i see that backend is initializing sockets in api.js
by:
.configure(socketio({ path: '/ws' }))
but i highly doubt this error is related to that since other sockets requests on the client side are working fine. This error only occurs after the app has hot reloaded. Which is a bit odd!
Note the websockets
call failing which is right after a hot reload!
This is the normal behavior, the server restarts and the connection is lost for a short time.
Simply cloned and build in dev
Getting this error after changing content in any of the components. Basically hot reload is causing this:
Any suggestions? Anyone else getting this?