Ari Perkkiö

/pkg-pr-new

Publis script ran on https://github.com/AriPerkkio/eslint-remote-tester/actions/runs/10561403104/job/29257063251 > ⚡️ Your npm packages are published. > eslint-remote-tester: npm i https://pkg.pr.new/eslint-remote-tester@0f4f5aa > eslint-remote-tester-repositories: npm i https://pkg.pr.new/eslint-remote-tester-repositories@0f4f5aa `0f4f5aa` is latest on `master`, it should have...

I think this was attempted in https://github.com/vitest-dev/vitest/pull/5791 but rejected eventually. You should be able to do this by using different pools though: ```ts import { defineConfig } from "vitest/config"; const...

> I have a [POC here](https://github.com/vitest-dev/vitest/commit/625afd4c407bcf7e259df6e465794c63f9558d87) That still would not change isolation option of the pool. It's only affecting the worker's isolation option. The pool-level isolation is where the speed...

This will be possible to implement after https://github.com/vitest-dev/vitest/pull/8705

@paulintrognon after #8705 it's now possible to configure isolation per project. - https://vitest.dev/guide/recipes.html#disabling-isolation-for-specific-test-files-only I would also recommend to define unique [`sequence.groupOrder`](https://vitest.dev/config/#grouporder) for the projects in that case.

Collecting time of every file that was loaded sounds a bit extreme. Currently Vitest tracks only the time the whole test file took to load. Using custom reporter you can...

> I expected there to be an option like `slowTestThreshold`, and then show everything that is above that treashold. Maybe `slowCollectThreshold`? This reporting feature is still about just `collect` phase,...

Perfect, thanks! Also make sure to replace the `workspace` config option with `projects`. It requires Vitest `^3.2`. The `4.beta` removes `workspace` option compeltely.

@edison1105 I've rebased latest `main` to this branch and it's ready to go. Are you able to re-open this PR? Github doesn't allow me to do that. If not, I'll...