Allow passing the same filtering options from the interactive CLI as arguments/config

[perebusquets]

Hi, awesome project!

I'm opening this issue due to the need of working in a monorepo, and using Vitetest projects. The need is similar to the one stated in this issue #155 , but in our case we use a single config file (which evalite is able to pick up) just with a different project config for each suite of test types (ie, unit, e2e, performance, eval,...).

I think we could achieve this in two ways:

• I can see that, in the interactive CLI, if you press w you're able to filter by project and it works as intended, the thing is that it would be extremely useful to have the same options as command arguments (like the ones in vitest, for example --project in this case). However l'm not sure if that's something coming from evalite or from the vitest runner directly.

• The other way we could implement this is via the evalite.config.ts, having an option (for example, vitestProject) and setting that to the vitest runner.

This way, we could use the evalite CLI (instead of using vitest directly) and choose which configuration of Vite to use depending on the argument flag/evalite config.

Thank you for your time and this awesome test suite!

[mattpocock]

Agree that this is definitely needed. We support path but not other vitest-based options.

@claude do some initial investigative work to explore what options Vitest exposes via the programmatic node API. Return back a report on how feasible it would be to add this to our existing setup.

[claude]

Claude Code is working…

I'll analyze this and get back to you.

View job run