Strict mode violation in Chrome (with fix)

[asdf072]

I recently started getting an error in Chrome. [Exception: TypeError: 'caller', 'callee', and 'arguments' properties may not be accessed on strict mode functions or the arguments objects for calls to them at Function.

I tracked it down to the timeout function in the this.open method. The function in the setTimeout makes a direct call to websocket.close(). Line #227.

Using func.call() to help it define this seems to have cleared up the error. Can anyone see any unintended issues?

            var localWs = ws;
            var timeout = setTimeout(function() {
                if (self.debug || ReconnectingWebSocket.debugAll) {
                    console.debug('ReconnectingWebSocket', 'connection-timeout', self.url);
                }
                timedOut = true;
                //localWs.close(); // this causes a strict mode violation
                localWs.close.call(localWs); // better
                timedOut = false;
            }, self.timeoutInterval);

[asdf072]

But now, minifying breaks it ... Hm

[Tangee69]

• @

[bj00rn]

@asdf072 try the fork project at https://github.com/partykit/partykit/tree/main/packages/partysocket and file an issue there if problem still