The websocket resolution logic here attempts to resolve WebSocket on global and window before defaulting to the Node ws implementation.
This turns out to be non-exhaustive, since there is a WebSocket built-in in the extension env (i.e. just WebSocket or self.WebSocket) but no window which it would normally resolve to in a browser env.
Context
globalandwindowbefore defaulting to the Nodewsimplementation.WebSocketorself.WebSocket) but nowindowwhich it would normally resolve to in a browser env.