Ari Perkkiö

I was able to reproduce this issue using just Node API's and `undici`: https://github.com/nodejs/undici/issues/2026 I didn't look into their codebase that much but there seems to be some native code:...

> Has there been any further investigation to the root cause of this? I am running into it running in Azure Devops as well but do not use the above...

Node's `fetch` doesn't get stuck when run inside `node:child_processs`. It's only the `node:worker_threads` which has these issues. On Vitest you can use `--pool=forks` to run all tests inside `node:child_process`. Or...

```ts // @vitest-environment happy-dom import { test } from "vitest"; import nodeFetch from "node-fetch"; test("fetch", () => { console.log(fetch === nodeFetch); // stdout | tests/happy-dom.test.ts > fetch // false });...

@InfiniteXyy I don't think that is related to this issue as it's not using `fetch`. You should file separate bug with that minimal reproduction case instead.

Any thoughts about this approach @SimenB and @bcoe? In Vitest we will always have source maps available so we can utilize those for analysing the source file. I believe Jest...

@joshuanathanson - just curious, what test runner and coverage tool are you using this commit with?

You can't mix Istanbul instrumented coverage with V8 coverage. Use the same instrumenter for both test setups. E.g. change `'babel'` here to use istanbul with Jest: https://github.com/samhatoum/monorepro/blob/c6203edacde44b93eb5a48cf09feaea9b408ade0/jest.config.ts#L6

@hmajid2301 in your case one of the Svelte file imports is unable to tree shake imports. This seems to take most of the time. ```ts import { FolderSolid } from...

It's the `gui/node_modules/svelte-awesome-icons/index.js`. But as said, the package itself seems fine. It's just Vitest which ends up processing all the files imported in that entrypoint. In your case it's possible...