vitest: Error: [birpc] timeout on calling "fetch"

Describe the bug

Getting Error: [birpc] timeout on calling "fetch" repeatedly after upgrading

Reproduction

https://github.com/Maxim-Mazurok/vite-repro

System Info

System:
    OS: Windows 11 10.0.22621
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i9-12900H
    Memory: 27.99 GB / 63.68 GB
  Binaries:
    Node: 20.10.0 - ~\AppData\Local\nvs\node\20.10.0\x64\node.EXE
    npm: 10.2.3 - ~\AppData\Local\nvs\node\20.10.0\x64\npm.CMD
  Browsers:
    Edge: Chromium (121.0.2277.83)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    @vitest/coverage-v8: 1.0.4 => 1.0.4
    @vitest/ui: 1.0.4 => 1.0.4
    vite: >=5.1.1 => 5.1.1
    vitest: 1.0.4 => 1.0.4

Used Package Manager

npm

Validations

Follow our Code of Conduct
Read the Contributing Guidelines.
Read the docs.
Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
The provided reproduction is a minimal reproducible example of the bug.

About this issue

Original URL
State: closed
Created 5 months ago
Reactions: 9
Comments: 17 (7 by maintainers)

Most upvoted comments

The fix on Vite side is released in 5.1.6 (https://github.com/vitejs/vite/pull/16124).

sapphi-red on Mar 13, 2024

By the way, the workaround is to remove references from tsconfig:

{
  "extends": "../tsconfig.base.json",
  "compilerOptions": {
    "module": "commonjs",
    "forceConsistentCasingInFileNames": true,
    "strict": true,
    "noImplicitOverride": true,
    "noPropertyAccessFromIndexSignature": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true
  },
  "files": [],
  "include": [],
-  "references": [
-    {
-      "path": "./tsconfig.lib.json"
-    },
-    {
-      "path": "./tsconfig.spec.json"
-    }
-  ]
}

sheremet-va on Feb 13, 2024

This is happening for 2/20 nx projects I have. And only happens on vite 5.1.x but works fine on 5.0.x

Maxim-Mazurok on Feb 11, 2024

strange, for me only --pool=forks cli option works, setting it inside vitest.config.js has no effect.

viceice on Mar 11, 2024

@daihere1993 Ah, apologies, I misread the extends in your original post which caused my confusion. Thanks for pointing that out. Makes sense.

chinanderm on Feb 27, 2024

I’m also facing this error while running tests in a nx wprkspace with vite@5.1.1 but working fine with vite@5.0.12

ak274 on Feb 12, 2024