Closed JackWilb closed 4 years ago
Any ideas what might be causing this @waxlamp?
This happens when you visit multinet.app from your browser?
It definitely looks like it's what you said, coming from the webpack dev server.
I think we can resolve this sort of thing by being more careful about how we serve our production sites.
Now that we're serving in production mode from our deployment, this is fixed.
There seems to be an infinitely looping error on my machine where firefox (also verified that this happens in chrome) keeps trying to connect to a websocket. This goes on until I close the page. The full error is below. Is this caused by webpack thinking that it's a dev server and not the prod server?