Fix: reconnect() not working after maxRetries exhausted

[threepointone]

Summary

Fixes cloudflare/partykit#252 — calling ws.reconnect() after maxRetries has been exhausted now correctly resets and initiates a new connection.

Problem

In _connect(), when maxRetries is reached, the method acquires _connectLock = true but returns early without releasing it. This leaves the lock permanently held, so any subsequent call to reconnect() (which resets _retryCount and calls _connect()) silently bails out at the lock check — making it impossible to manually reconnect after automatic retries are exhausted.

This is a common scenario when a user wants to force a reconnection on window focus after the tab has been inactive and retries have been spent.

Fix

Release _connectLock before the early return in the maxRetries guard inside _connect():

 if (this._retryCount >= maxRetries) {
   this._debug("max retries reached", this._retryCount, ">=", maxRetries);
+  this._connectLock = false;
   return;
 }

Test plan

• Added a test that connects to an unreachable URL with maxRetries: 0, waits for retries to exhaust, then calls reconnect() with a valid URL and verifies the connection opens successfully.
• All existing 38 tests in reconnecting.test.ts continue to pass.

[changeset-bot]

🦋 Changeset detected

Latest commit: 5383192

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
partysocket	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR