Ari Perkkiö

Hey @gtbuchanan, do you have any time to finalize this PR? I'm also happy to take over and finish it if you prefer that. Thanks for all the work so...

Some type declarations are importing types from `vite`. There's `/// ` in `vite/dist/node/index.d.ts`.

It's possible if you run Vitest in watch-mode and open browser's dev-tools.

To run in watch mode, remove the `run` part from here: https://github.com/gezilinll/vitest-browser-debugger/blob/51542b5af37f932ba35643190191e0961b23c70c/package.json#L5-L7 ```diff "scripts": { - "test": "vitest run" + "test": "vitest" }, ```

Debugger in VS code works fine with breakpoints with these settings: ```ts // vitest.config.ts import { defineConfig } from "vitest/config"; export default defineConfig({ test: { browser: { enabled: true, name:...

I don't have access to IntelliJ, but you should be able to get it working with these instructions: https://www.jetbrains.com/help/idea/configuring-javascript-debugger.html It's just about connecting to Chrome Devtools Protocol, not really Vitest...

For VS Code you can also create a single configuration file. This will run Vitest and attach to the browser. ```json { "version": "0.2.0", "configurations": [ { "type": "node", "request":...

I want to highlight how many new downloads a package has got in specific timeframe, while displaying the overall graph. This would indicate the speed of growth. Here I would...

> Like running `e2e` and `unit` tests from separate commands. You have have 50, 100+ packages with tests, listing them all out in the `--project` command is.... less than ideal....

The `test/cli/test/vm-threads.test.ts` is also failing on CI and locally now. The failure does not happen with Node `22.0`, but happens with all versions above `22.1`. ```sh ari ~/x/vitest/test/cli (main) $...