I tried to use WebSocket in Vue and found it unsuccessful

[LunckyB]

I tried to use WebSocket in Vue and found it unsuccessful, Does Wails not support it?

[raguay]

I believe it's the same issue as Tauri and Wails: websockets is only allows from a https source. Therefore, you can't use the ws:// designation. It's an issue with the built in browser for the operating system that Wails makes use of. I think the best solution is to create the functionality in the application go code and use signals to alert the front-end.

[LunckyB]

I believe it's the same issue as Tauri and Wails: websockets is only allows from a https source. Therefore, you can't use the ws:// designation. It's an issue with the built in browser for the operating system that Wails makes use of. I think the best solution is to create the functionality in the application go code and use signals to alert the front-end.

Thank you for your reply. I now use Gorilla/Websocket in Wails

[misitebao]

I strongly recommend that the front-end part is only used to display UI, js is only used to handle front-end interaction logic and call Go, other business logic and communication should be done by Go, otherwise it will make the Wails application look like a shell, but in fact It can do more than that.

[leaanthony]

☝️ This is the recommended best practice.

[TheFranconianCoder]

Especially when the logical part is in Go, interactive response in the GUI is often necessary. WebSockets is default for such channels. But because it's way simpler, I personally switched to server-sent events for such topics. It has limitations compared to WebSockets, but works very well for some event transfer.

[PungYoung]

I'm also developing 'webssh' recently, which just solves this problem vue3： const webSocket = new WebSocket(WebSocketAddr)

go："github.com/gorilla/websocket"

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[leaanthony]

Sounds like there's a workaround. Closing.