Process completed with exit code 1.

Process completed with exit code 1.

Prefer using an optional chain expression instead, as it's more concise and easier to read.

Prefer using an optional chain expression instead, as it's more concise and easier to read.

Do not delete dynamically computed property keys.

Do not delete dynamically computed property keys.

Process completed with exit code 1.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, dkhunt27/action-nx-affected-list@v6.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Identifier 'beforeEach' is imported but never used.

Identifier 'afterEach' is imported but never used.

Identifier 'vi' is imported but never used.

Identifier 'beforeEach' is imported but never used.

Identifier 'afterEach' is imported but never used.

Identifier 'hasSpanStreamingEnabled' is imported but never used.

Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: dev-packages/e2e-tests/test-applications/tanstackstart-react/package.json, dev-packages/e2e-tests/test-applications/tanstackstart-react/src/globals.d.ts, dev-packages/e2e-tests/test-applications/tanstackstart-react/src/router.tsx, dev-packages/e2e-tests/test-applications/tanstackstart-react/src/routes/custom-monitor.ts, dev-packages/e2e-tests/test-applications/tanstackstart-react/tests/errors.test.ts, dev-packages/e2e-tests/test-applications/tanstackstart-react/tests/middleware.test.ts, dev-packages/e2e-tests/test-applications/tanstackstart-react/tests/transaction.test.ts, dev-packages/e2e-tests/test-applications/tanstackstart-react/tests/tunnel.test.ts, dev-packages/e2e-tests/test-applications/tanstackstart-react/vite.config.ts, packages/tanstackstart-react/src/client/sdk.ts, packages/tanstackstart-react/src/client/tunnelRoute.ts, packages/tanstackstart-react/src/server/index.ts, packages/tanstackstart-react/src/server/tunnelRoute.ts, packages/tanstackstart-react/src/vite/index.ts, packages/tanstackstart-react/src/vite/sentryTanstackStart.ts, packages/tanstackstart-react/src/vite/tunnelRoute.ts, packages/tanstackstart-react/test/client/sdk.test.ts, packages/tanstackstart-react/test/client/tunnelRoute.test.ts, packages/tanstackstart-react/test/server/tunnelRoute.test.ts, packages/tanstackstart-react/test/vite/sentryTanstackStart.test.ts, packages/tanstackstart-react/test/vite/tunnelRoute.test.ts Sample coverage paths: ./mute.js, /Users/isaacs/dev/js/events-to-array/etoa.js This usually indicates a path format mismatch between your coverage tool and the repository.

Please ensure your test framework is generating JUnit XML output.

No JUnit XML files found matching pattern: **/*.junit.xml

No files found matching pattern: **/*.junit.xml

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./dev-packages/size-limit-gh-action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

12 skipped 1 passed (4.7s)

12 skipped 1 passed (4.7s)

12 skipped 1 passed (4.3s)

12 skipped 1 passed (2.3s)

12 skipped 1 passed (2.3s)

12 skipped 1 passed (3.3s)