Closed shroominic closed 1 year ago
There is a placeholder for websockets (in apiCore) but I'm not sure what could be calling it. So ... it's probably not the stack.
What it could be is the hot-reload in the Nuxt dev environment which does use sockets to check for code changes. You might want to try refreshing your Nuxt / yarn install (delete the .nuxt
and node_modules
folders in frontend
and then yarn install
again).
Thanks, it was something nuxt related so I fixed it by putting watch: false,
inside the nuxt.config.ts/content dict
I don't know what is happening or where this is coming from but the client is constantly trying to connect to this web socket and failing ...