TypeError: Cannot read properties of null (reading 'code') ❯ tests/integration/integration.test.ts:10:21 ❯ ChildProcess.exithandler node:child_process:413:7 ❯ ChildProcess.emit node:events:520:28 ❯ maybeClose node:internal/child_process:1105:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:305:5 This error originated in "tests/integration/integration.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 "outputs accessibility violation information for the demo app". 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: Cannot read properties of null (reading 'code') ❯ tests/integration/integration.test.ts:25:23 ❯ ChildProcess.exithandler node:child_process:413:7 ❯ ChildProcess.emit node:events:520:28 ❯ maybeClose node:internal/child_process:1105:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:305:5 This error originated in "tests/integration/integration.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 "filters the components to run". 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: Cannot read properties of null (reading 'code') ❯ tests/integration/integration.test.ts:41:23 ❯ ChildProcess.exithandler node:child_process:413:7 ❯ ChildProcess.emit node:events:520:28 ❯ maybeClose node:internal/child_process:1105:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:305:5 This error originated in "tests/integration/integration.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 "fails only specific impact levels if specified". 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: Cannot read properties of null (reading 'code') ❯ tests/integration/integration.test.ts:57:23 ❯ ChildProcess.exithandler node:child_process:413:7 ❯ ChildProcess.emit node:events:520:28 ❯ maybeClose node:internal/child_process:1105:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:305:5 This error originated in "tests/integration/integration.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 "accepts a port to run on". 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.

Process completed with exit code 1.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/