Closed doox911-opensource closed 6 months ago
Hey there, thanks for reporting the issue
Could you provide a repro and share with us the result of running quasar info
in your project?
Hey there, thanks for reporting the issue Could you provide a repro and share with us the result of running
quasar info
in your project?
Sure, I've updated the issue
Could you make sure all your deps are up-to-date to latest stable versions?
Btw, this is what is meant when we ask for a "repro": https://antfu.me/posts/why-reproductions-are-required#reproducible-projects-or-playgrounds
Could you make sure all your deps are up-to-date to latest stable versions?
Btw, this is what is meant when we ask for a "repro": https://antfu.me/posts/why-reproductions-are-required#reproducible-projects-or-playgrounds
https://stackblitz.com/edit/quasarframework-vhjaht?file=vitest.config.ts
Apparently there's a mismatch with Plugin types that Vitest expect in its configuration and plugin types that Vite provide This happens when there's a Vite version mismatch / Vite dep is duplicated somehow
Apparently latest Vite version changed the Plugin type signature and that's making Vitest angry since Quasar still only supports up to Vite 3, and will switch directly to Vite 5
Try using resolutions to force Vite 4 usage, as shown here
I'll try to come up with an automatic workaround for this as time permits, but being on the verge of both Vitest stable release and Vite 5 stable release (and with both still making breaking changes), it may be worth still waiting them to stabilize before actually solving this
I confirm the issue is with a mismatch between @quasar/app-vite
and vitest
version of vite
Applying the pointed out workaround is the solution for the alpha version of this package (aka up to v0.4)
Next Vitest AE version (v1 beta) will jump straight to Vite 5 and rely on @quasar/app-vite
v2, thus the problem will be solved
@IlCallo Thank you for the explanation. I had the same problem and I'll keep it that way until they fix it.
You can see an example setup of Vitest 0.34 working with Vite 4 and @quasar/app-vite
v1 here: https://github.com/quasarframework/quasar-testing/tree/vitest-alpha/test-vite-app-v1
Important bit: https://github.com/quasarframework/quasar-testing/blob/cc3b4377385433448c03c06217d08c1085f04271/test-vite-app-v1/package.json#L64-L70
You can see an example setup of Vitest 1.1 working with Vite 5 and @quasar/app-vite
v1 here: https://github.com/quasarframework/quasar-testing/tree/feature/vitest-v1/test-vite-app-v1-vite5
You can see an example setup of Vitest 1.1 working with Vite 5 and @quasar/app-vite
v2 here: https://github.com/quasarframework/quasar-testing/tree/feature/vitest-v1/test-vite-app-v2
Important bit: https://github.com/quasarframework/quasar-testing/blob/13bc241433a06d6bcc943d3eca90c072f86b3865/test-vite-app-v2/package.json#L48
Created
vitest.config.ts
:Is it just me who has such a problem or has someone else encountered it?
Next, I run
yarn run test:unit:ui
:quasar info
:I have an error
error Command failed with exit code 43.
, but the interface starts.