Since the longest time activist has been dealing with a constant stream of errors in development logs like the following:
WebSocket connection to 'ws://[localhost:4000/ws](http://localhost:4000/ws)' failed: Could not connect to the server.
Everything is generally working fine, and they're mostly a major annoyance to the development experience when it comes to checking actual errors/warnings. Via investigations, they are directly related to Nuxt Content, with at least a temporary fix coming in the configuration directions.
Terms
Behavior
Since the longest time activist has been dealing with a constant stream of errors in development logs like the following:
Everything is generally working fine, and they're mostly a major annoyance to the development experience when it comes to checking actual errors/warnings. Via investigations, they are directly related to Nuxt Content, with at least a temporary fix coming in the configuration directions.