No overload matches this call.

No overload matches this call.

No overload matches this call.

No overload matches this call.

No overload matches this call.

No overload matches this call.

No overload matches this call.

No overload matches this call.

No overload matches this call.

No overload matches this call.

TypeError: isWithComponents is not a function ❯ getComponentProps src/services/createPropStore.ts:120:9 ❯ Object.setProps src/services/createPropStore.ts:58:42 ❯ set src/services/createRouter.ts:145:15 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 ❯ Object.start src/services/createRouter.ts:294:5 ❯ src/components/routerView.browser.spec.ts:25:3 ❯ node_modules/@vitest/runner/dist/index.js:533:5 ❯ runTest node_modules/@vitest/runner/dist/index.js:1056:11 ❯ runSuite node_modules/@vitest/runner/dist/index.js:1205:15 This error originated in "src/components/routerView.browser.spec.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 "src/components/routerView.browser.spec.ts". 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.

TypeError: isWithComponents is not a function ❯ getComponentProps src/services/createPropStore.ts:120:9 ❯ Object.setProps src/services/createPropStore.ts:58:42 ❯ set src/services/createRouter.ts:145:15 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 ❯ Object.start src/services/createRouter.ts:294:5 ❯ src/components/routerView.browser.spec.ts:57:3 ❯ node_modules/@vitest/runner/dist/index.js:533:5 ❯ runTest node_modules/@vitest/runner/dist/index.js:1056:11 ❯ runSuite node_modules/@vitest/runner/dist/index.js:1205:15 This error originated in "src/components/routerView.browser.spec.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 "src/components/routerView.browser.spec.ts". 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.

TypeError: isWithComponents is not a function ❯ getComponentProps src/services/createPropStore.ts:120:9 ❯ Object.setProps src/services/createPropStore.ts:58:42 ❯ set src/services/createRouter.ts:145:15 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 ❯ start src/services/createRouter.ts:294:5 This error originated in "src/components/routerView.browser.spec.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 "src/components/routerView.browser.spec.ts". 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.

TypeError: isWithComponents is not a function ❯ getComponentProps src/services/createPropStore.ts:120:9 ❯ Object.setProps src/services/createPropStore.ts:58:42 ❯ set src/services/createRouter.ts:145:15 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 ❯ start src/services/createRouter.ts:294:5 This error originated in "src/components/routerView.browser.spec.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 "src/components/routerView.browser.spec.ts". 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.

TypeError: isWithComponents is not a function ❯ getComponentProps src/services/createPropStore.ts:120:9 ❯ Object.setProps src/services/createPropStore.ts:58:42 ❯ set src/services/createRouter.ts:145:15 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 ❯ Object.start src/services/createRouter.ts:294:5 ❯ src/components/routerView.browser.spec.ts:154:3 ❯ node_modules/@vitest/runner/dist/index.js:533:5 ❯ runTest node_modules/@vitest/runner/dist/index.js:1056:11 ❯ runSuite node_modules/@vitest/runner/dist/index.js:1205:15 This error originated in "src/components/routerView.browser.spec.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 "src/components/routerView.browser.spec.ts". 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.

TypeError: isWithComponents is not a function ❯ getComponentProps src/services/createPropStore.ts:120:9 ❯ Object.setProps src/services/createPropStore.ts:58:42 ❯ set src/services/createRouter.ts:145:15 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 ❯ Object.start src/services/createRouter.ts:294:5 ❯ src/components/routerView.browser.spec.ts:178:3 ❯ node_modules/@vitest/runner/dist/index.js:533:5 ❯ runTest node_modules/@vitest/runner/dist/index.js:1056:11 ❯ runSuite node_modules/@vitest/runner/dist/index.js:1205:15 This error originated in "src/components/routerView.browser.spec.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 "src/components/routerView.browser.spec.ts". 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.

TypeError: isWithComponents is not a function ❯ getComponentProps src/services/createPropStore.ts:120:9 ❯ Object.setProps src/services/createPropStore.ts:58:42 ❯ set src/services/createRouter.ts:145:15 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 ❯ Object.start src/services/createRouter.ts:294:5 ❯ src/components/routerView.browser.spec.ts:211:3 ❯ node_modules/@vitest/runner/dist/index.js:533:5 ❯ runTest node_modules/@vitest/runner/dist/index.js:1056:11 ❯ runSuite node_modules/@vitest/runner/dist/index.js:1205:15 This error originated in "src/components/routerView.browser.spec.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 "src/components/routerView.browser.spec.ts". 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.

TypeError: isWithComponents is not a function ❯ getComponentProps src/services/createPropStore.ts:120:9 ❯ Object.setProps src/services/createPropStore.ts:58:42 ❯ set src/services/createRouter.ts:145:15 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 ❯ Object.start src/services/createRouter.ts:294:5 ❯ src/components/routerView.browser.spec.ts:239:3 ❯ node_modules/@vitest/runner/dist/index.js:533:5 ❯ runTest node_modules/@vitest/runner/dist/index.js:1056:11 ❯ runSuite node_modules/@vitest/runner/dist/index.js:1205:15 This error originated in "src/components/routerView.browser.spec.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 "src/components/routerView.browser.spec.ts". 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.

TypeError: isWithComponents is not a function ❯ getComponentProps src/services/createPropStore.ts:120:9 ❯ Object.setProps src/services/createPropStore.ts:58:42 ❯ set src/services/createRouter.ts:145:15 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 ❯ Object.start src/services/createRouter.ts:294:5 ❯ src/components/routerView.browser.spec.ts:273:3 ❯ node_modules/@vitest/runner/dist/index.js:533:5 ❯ runTest node_modules/@vitest/runner/dist/index.js:1056:11 ❯ runSuite node_modules/@vitest/runner/dist/index.js:1205:15 This error originated in "src/components/routerView.browser.spec.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 "src/components/routerView.browser.spec.ts". 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.

TypeError: isWithComponents is not a function ❯ getComponentProps src/services/createPropStore.ts:120:9 ❯ Object.setProps src/services/createPropStore.ts:58:42 ❯ set src/services/createRouter.ts:145:15 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 ❯ Object.start src/services/createRouter.ts:294:5 ❯ src/components/routerView.browser.spec.ts:313:3 ❯ node_modules/@vitest/runner/dist/index.js:533:5 ❯ runTest node_modules/@vitest/runner/dist/index.js:1056:11 ❯ runSuite node_modules/@vitest/runner/dist/index.js:1205:15 This error originated in "src/components/routerView.browser.spec.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 "src/components/routerView.browser.spec.ts". 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.

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636