Process completed with exit code 1.

ReferenceError: mockWebSocketDefaultImplementation is not defined ❯ t.<anonymous> src/connection.test.ts:464:24 ❯ src/connection.ts:254:18 ❯ Connection.openWebSocket src/connection.ts:230:12 ❯ ws.retryOn.default.child.attempt.attempt src/connection.ts:196:14 ❯ performAttempt src/api-utils.ts:82:23 ❯ asyncOperationWithRetry src/api-utils.ts:94:29

ReferenceError: Cannot access 'ws' before initialization ❯ cleanup src/connection.ts:247:9 ❯ EventTarget.onAbort src/connection.ts:233:9 ❯ EventTarget.[nodejs.internal.kHybridDispatch] node:internal/event_target:831:20 ❯ EventTarget.dispatchEvent node:internal/event_target:766:26 ❯ abortSignal node:internal/abort_controller:370:10 ❯ AbortController.abort node:internal/abort_controller:392:5 ❯ EventTarget.onSignalAbort src/api-utils.ts:178:46 ❯ EventTarget.[nodejs.internal.kHybridDispatch] node:internal/event_target:831:20 ❯ EventTarget.dispatchEvent node:internal/event_target:766:26 ❯ abortSignal node:internal/abort_controller:370:10 This error originated in "src/connection.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "maps results to the correct execution if they are received out of order". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

ReferenceError: Cannot access 'ws' before initialization ❯ cleanup src/connection.ts:247:9 ❯ EventTarget.onAbort src/connection.ts:233:9 ❯ EventTarget.[nodejs.internal.kHybridDispatch] node:internal/event_target:831:20 ❯ EventTarget.dispatchEvent node:internal/event_target:766:26 ❯ abortSignal node:internal/abort_controller:370:10 ❯ AbortController.abort node:internal/abort_controller:392:5 ❯ EventTarget.onSignalAbort src/api-utils.ts:178:46 ❯ EventTarget.[nodejs.internal.kHybridDispatch] node:internal/event_target:831:20 ❯ EventTarget.dispatchEvent node:internal/event_target:766:26 ❯ abortSignal node:internal/abort_controller:370:10 This error originated in "src/connection.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "maps results to the correct execution if they are received out of order". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

ReferenceError: Cannot access 'ws' before initialization ❯ cleanup src/connection.ts:247:9 ❯ EventTarget.onAbort src/connection.ts:233:9 ❯ EventTarget.[nodejs.internal.kHybridDispatch] node:internal/event_target:831:20 ❯ EventTarget.dispatchEvent node:internal/event_target:766:26 ❯ abortSignal node:internal/abort_controller:370:10 ❯ AbortController.abort node:internal/abort_controller:392:5 ❯ EventTarget.onSignalAbort src/api-utils.ts:178:46 ❯ EventTarget.[nodejs.internal.kHybridDispatch] node:internal/event_target:831:20 ❯ EventTarget.dispatchEvent node:internal/event_target:766:26 ❯ abortSignal node:internal/abort_controller:370:10 This error originated in "src/connection.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "maps results to the correct execution if they are received out of order". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.