Ari Perkkiö

That doesn't sound too bad. I've seen cases where CIs get slow when `coverage/tmp` reaches +450 MB. The process may seem stuck but it's actually just processing a lot of...

Try adding `NODE_DEBUG: 'c8'` environment variable to see if `c8` logs any errors.

> I am transitioning from Jest to Vitest, which uses C8 to generate the coverage report. This is fixed in Vitest v1.6 and v2: https://github.com/vitest-dev/vitest/pull/5457. It's no longer `c8` related...

Here's minimal reproduction case without any 3rd party dependencies: https://stackblitz.com/~/edit/vite-cyclic-imports-vs-node?file=load-with-vite.mjs&file=load-with-node.mjs > ``` > $ node ./load-with-vite.mjs > > 10:36:04 [vite] Error when evaluating SSR module /ion-js/dom/Blob.js: > |- TypeError: Cannot...

Adding custom `tsup` hook that restarts the storybook dev server improves developer experience a bit. You'll still have to manually refresh the browser, but at least changes are reloaded automatically:...

Could you set up a minimal reproduction for this? Or maybe solve this by not checking types of your dependencies by using `skipLibCheck` in `tsconfig.json`?

Similar issue from Piscina: https://github.com/piscinajs/piscina/issues/426 Tinypool should apply similar changes as in https://github.com/piscinajs/piscina/pull/433.

@aleclarson is this feature request still valid? It seems 2 years old by now.

> There are some ts errors in the tests: `task-queue.test.ts` and `uncaught-exception-from-handler.test.ts` Typescript is a bit more strict now. I can fix these after merging this PR as it seems...

This feature has been included in Vitest v1.6 and enabled by default in [Vitest v2](https://github.com/vitest-dev/vitest/releases/tag/v2.0.0) for ~2 weeks now. We haven't (yet) heard any issues about this change. @bcoe there...