Vitest support

[cexbrayat]

I spotted a comment in a recent commit about Vitest support.

That would be great, and probably a better alternative than Jest support.

I would be willing to help move this forward if nobody is working on this

I suppose we would add a --vitest flag.

How do you plan to integrate with the current --tests flag?

Something like: if both --cypress and --vitest are present, use Vitest for unit test, and use Cypress for e2e, otherwise, if only cypress is present, use it for both (as --tests does now)?

It will also add other combinations for the playground: is it OK? (jsx-pinia-vitest, jsx-pinia-cypress, jsx-pinia-vitest-cypress, jsx-router-vitest, etc...)

[haoqunjiang]

I would be willing to help move this forward if nobody is working on this

That will be great!

I suppose we would add a --vitest flag.

Agree.

How do you plan to integrate with the current --tests flag?

Something like: if both --cypress and --vitest are present, use Vitest for unit test, and use Cypress for e2e, otherwise, if only cypress is present, use it for both (as --tests does now)?

Mostly agree.
I suggest that we change how --test/--with-tests works now, defaulting to Vitest for unit test and Cypress for e2e. Because Vitest works better in headless CI environments than Cypress Component Testing.

--cypress without --vitest can use Cypress for both unit and e2e tests.

It will also add other combinations for the playground: is it OK? (jsx-pinia-vitest, jsx-pinia-cypress, jsx-pinia-vitest-cypress, jsx-router-vitest, etc...)

Yeah, that's totally fine.

[haoqunjiang]

Implemented at #29

[haoqunjiang]

Released as 3.1.0