You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Nuxt 3, we had (semi-official) solutions to support WebSocket in development and production but never a standard layer. This had been something we planned to support universally in nuxt/nitro dev server and runtime.
With the introduction of new dev server CLI architecture in nuxi 3.7 (#81) some of the current solutions stooped to be working.
My plan is to first make sure there is a basic replacement for current solutions and then put the stable WS layer on fast track to finally resolve this. (Update: hooking to the server upgrade via listen should work again now via #127)
[description is wip]
Since Nuxt 3, we had (semi-official) solutions to support WebSocket in development and production but never a standard layer. This had been something we planned to support universally in nuxt/nitro dev server and runtime.
With the introduction of new dev server CLI architecture in nuxi 3.7 (#81) some of the current solutions stooped to be working.
My plan is to first make sure there is a basic replacement for current solutions and then put the stable WS layer on fast track to finally resolve this. (Update: hooking to the server
upgrade
vialisten
should work again now via #127)Related issues:
nitro.devProxy
for websocket is not working #107The text was updated successfully, but these errors were encountered: