fix: do not reconnect on intentional socket close

[o19k]

Summary

Calling socketClient.close() triggers the underlying socket.close(), which fires the onClose callback, which calls attemptReconnect(). This causes the socket to reconnect even when the caller explicitly wanted to close it — resulting in the node process never exiting.

Root cause: attemptReconnect() had no way to distinguish between an intentional close and an unexpected socket drop.

Fix: Added an intentionallyClosed flag (closure-scoped, mirrors the existing reconnectInProgress pattern). Set to true in socketClient.close() before calling socket.close(). Checked in attemptReconnect() to skip reconnection.

Fixes #4378

Test plan

• reconnect on socket-level close — verifies unexpected socket drops still trigger reconnect
• does not reconnect on intentional close — verifies socketClient.close() no longer reconnects
• close does not reconnect (webSocket integration test) — end-to-end with a real WebSocket

[changeset-bot]

🦋 Changeset detected

Latest commit: e04dd9b

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

This PR includes changesets to release 1 package

Name	Type
viem	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

[vercel]

@o19k is attempting to deploy a commit to the Wevm Team on Vercel.

A member of the Team first needs to authorize it.