ReferenceError: window is not defined ❯ FrameScheduler.requestAnimationFrame src/core/renderer/utilities/FrameScheduler.js:41:4 ❯ PriorityQueue.schedulingCallback src/core/renderer/utilities/PriorityQueue.js:41:24 ❯ PriorityQueue.scheduleJobRun src/core/renderer/utilities/PriorityQueue.js:214:9 ❯ src/core/renderer/utilities/PriorityQueue.js:94:10 ❯ PriorityQueue.add src/core/renderer/utilities/PriorityQueue.js:81:18 ❯ test/core/PriorityQueue.test.js:35:9 This error originated in "test/core/PriorityQueue.test.js" 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 "should run jobs automatically in the correct 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: window is not defined ❯ FrameScheduler.requestAnimationFrame src/core/renderer/utilities/FrameScheduler.js:41:4 ❯ PriorityQueue.schedulingCallback src/core/renderer/utilities/PriorityQueue.js:41:24 ❯ PriorityQueue.scheduleJobRun src/core/renderer/utilities/PriorityQueue.js:214:9 ❯ src/core/renderer/utilities/PriorityQueue.js:94:10 ❯ PriorityQueue.add src/core/renderer/utilities/PriorityQueue.js:81:18 ❯ test/core/PriorityQueue.test.js:34:9 This error originated in "test/core/PriorityQueue.test.js" 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 "should run jobs automatically in the correct 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: window is not defined ❯ FrameScheduler.requestAnimationFrame src/core/renderer/utilities/FrameScheduler.js:41:4 ❯ PriorityQueue.schedulingCallback src/core/renderer/utilities/PriorityQueue.js:41:24 ❯ PriorityQueue.scheduleJobRun src/core/renderer/utilities/PriorityQueue.js:214:9 ❯ src/core/renderer/utilities/PriorityQueue.js:94:10 ❯ PriorityQueue.add src/core/renderer/utilities/PriorityQueue.js:81:18 ❯ test/core/PriorityQueue.test.js:33:9 This error originated in "test/core/PriorityQueue.test.js" 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 "should run jobs automatically in the correct 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: window is not defined ❯ FrameScheduler.requestAnimationFrame src/core/renderer/utilities/FrameScheduler.js:41:4 ❯ PriorityQueue.schedulingCallback src/core/renderer/utilities/PriorityQueue.js:41:24 ❯ PriorityQueue.scheduleJobRun src/core/renderer/utilities/PriorityQueue.js:214:9 ❯ src/core/renderer/utilities/PriorityQueue.js:94:10 ❯ PriorityQueue.add src/core/renderer/utilities/PriorityQueue.js:81:18 ❯ test/core/PriorityQueue.test.js:20:9 This error originated in "test/core/PriorityQueue.test.js" 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 "should process jobs in the order added if not priority callback is provided.". 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: window is not defined ❯ FrameScheduler.requestAnimationFrame src/core/renderer/utilities/FrameScheduler.js:41:4 ❯ PriorityQueue.schedulingCallback src/core/renderer/utilities/PriorityQueue.js:41:24 ❯ PriorityQueue.scheduleJobRun src/core/renderer/utilities/PriorityQueue.js:214:9 ❯ src/core/renderer/utilities/PriorityQueue.js:94:10 ❯ PriorityQueue.add src/core/renderer/utilities/PriorityQueue.js:81:18 ❯ test/core/PriorityQueue.test.js:19:9 This error originated in "test/core/PriorityQueue.test.js" 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 "should process jobs in the order added if not priority callback is provided.". 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: window is not defined ❯ FrameScheduler.requestAnimationFrame src/core/renderer/utilities/FrameScheduler.js:41:4 ❯ PriorityQueue.schedulingCallback src/core/renderer/utilities/PriorityQueue.js:41:24 ❯ PriorityQueue.scheduleJobRun src/core/renderer/utilities/PriorityQueue.js:214:9 ❯ src/core/renderer/utilities/PriorityQueue.js:94:10 ❯ PriorityQueue.add src/core/renderer/utilities/PriorityQueue.js:81:18 ❯ test/core/PriorityQueue.test.js:18:9 This error originated in "test/core/PriorityQueue.test.js" 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 "should process jobs in the order added if not priority callback is provided.". 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: window is not defined ❯ FrameScheduler.requestAnimationFrame src/core/renderer/utilities/FrameScheduler.js:41:4 ❯ PriorityQueue.schedulingCallback src/core/renderer/utilities/PriorityQueue.js:41:24 ❯ PriorityQueue.scheduleJobRun src/core/renderer/utilities/PriorityQueue.js:214:9 ❯ src/core/renderer/utilities/PriorityQueue.js:94:10 ❯ PriorityQueue.add src/core/renderer/utilities/PriorityQueue.js:81:18 ❯ test/core/PriorityQueue.test.js:17:9 This error originated in "test/core/PriorityQueue.test.js" 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 "should process jobs in the order added if not priority callback is provided.". 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: window is not defined ❯ FrameScheduler.requestAnimationFrame src/core/renderer/utilities/FrameScheduler.js:41:4 ❯ PriorityQueue.schedulingCallback src/core/renderer/utilities/PriorityQueue.js:41:24 ❯ PriorityQueue.scheduleJobRun src/core/renderer/utilities/PriorityQueue.js:214:9 ❯ src/core/renderer/utilities/PriorityQueue.js:94:10 ❯ PriorityQueue.add src/core/renderer/utilities/PriorityQueue.js:81:18 ❯ test/core/PriorityQueue.test.js:16:9 This error originated in "test/core/PriorityQueue.test.js" 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 "should process jobs in the order added if not priority callback is provided.". 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: window is not defined ❯ FrameScheduler.requestAnimationFrame src/core/renderer/utilities/FrameScheduler.js:41:4 ❯ PriorityQueue.schedulingCallback src/core/renderer/utilities/PriorityQueue.js:41:24 ❯ PriorityQueue.scheduleJobRun src/core/renderer/utilities/PriorityQueue.js:214:9 ❯ src/core/renderer/utilities/PriorityQueue.js:94:10 ❯ PriorityQueue.add src/core/renderer/utilities/PriorityQueue.js:81:18 ❯ test/core/PriorityQueue.test.js:15:9 This error originated in "test/core/PriorityQueue.test.js" 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 "should process jobs in the order added if not priority callback is provided.". 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: window is not defined ❯ FrameScheduler.requestAnimationFrame src/core/renderer/utilities/FrameScheduler.js:41:4 ❯ PriorityQueue.schedulingCallback src/core/renderer/utilities/PriorityQueue.js:41:24 ❯ PriorityQueue.scheduleJobRun src/core/renderer/utilities/PriorityQueue.js:214:9 ❯ src/core/renderer/utilities/PriorityQueue.js:94:10 ❯ PriorityQueue.add src/core/renderer/utilities/PriorityQueue.js:81:18 ❯ test/core/PriorityQueue.test.js:14:9 This error originated in "test/core/PriorityQueue.test.js" 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 "should process jobs in the order added if not priority callback is provided.". 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.

React Hook useMemo has a missing dependency: 'tiles'. Either include it or remove the dependency array

'Cesium' is not defined

'Cesium' is not defined