SignalR in Electron not working

[hillin]

We have a SignalR hub in our web app, consumed in the frontend with "@microsoft/signalr": "^8.0.0". It worked fine in browsers, but once they are packed into an Electron app (with Electron.NET), an error occurs when trying to connect to the hub:

Error: Failed to start the transport 'WebSockets': Error: ws does not work in the browser. Browser clients must use the native WebSocket object

I can pinpoint the issue down to the following code:

https://github.com/dotnet/aspnetcore/blob/4b8269fca79f95dc28c0c03546f941e86f663c15/src/SignalR/clients/ts/signalr/src/Utils.ts#L56C1-L58C6

Apparently in Electron's renderer process (frontend), the window.process object exists just like in node. In this case SignalR thought it was in a node environment and seek to ws for web socket transportation, which does not work because it's actually a browser environment.

[BrennanConroy]

Basically a duplicate of #49065
We'll use the other issue for tracking.

[dotnet-policy-service]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.