quasar ext add @quasar/testing-unit-vitest fails to recognize imports from @quasar/app-vite v2's '#q-app/wrappers'

[air-dex]

Reproduction

1. Sources migration

I've got a @quasar/app-vite v1's project that I have migrated to @quasar/app-vite v2 (v2.0.9). I followed Quasar Framework's migration guide: https://quasar.dev/quasar-cli-vite/upgrade-guide

I have followed the part with quasar/wrappers, especially fot boot files:

We have deprecated all the imports coming from quasar/wrappers. You can still use them, but we highly recommend switching to the new #q-app/wrappers, as shown below:

Hence my import { boot } from 'quasar/wrappers' have become import { defineBoot } from '#q-app/wrappers'

2. Tests migration

This project uses Vitest 2 for its unit testing. I have migrating tests using @quasar/testing-unit-vitest.

I have followed the evolutions you mention there: https://testing.quasar.dev/packages/unit-vitest/

I have encountered the #393 issue, that I have solved with the workaround I mentionned in it.

Expectations

Tests involving components should pass

Reality

Corresponding tests failed with the following error message: TypeError: defineBoot is not a function

Notes

1. Sorry for the lack of details but I cannot give you more of them.

2. Here is a workaround for it that works:

Replacing all the imports from '#q-app/wrappers' by imports from '@quasar/app-vite/wrappers'.

Example with boot files:

import { defineBoot } from '#q-app/wrappers' // KO
import { defineBoot } from '@quasar/app-vite/wrappers' // OK

Recommended Quasar's '#q-app/wrappers' should work, shouldn't they?

[IlCallo]

Hey there, could you try with the newly released Vitest AE version v1.2.1, reinstalling it and thus migrating to Vitest 3?
We noticed there was a Vite version mismatch introduced when @quasar/app-vite v2 was released as stable, here's an explanation

We just released and tested it into a freshly generate new app-vite v2 project

If it still doesn't work, the problem is probably in the migration guide from app-vite v1 to v2, more than in the Vitest AE

In those cases, a clean regeneration of the whole project scaffolded files will most probably fix those issues

[federicobohn-cs]

@IlCallo Im getting same issue. I made a fresh install with latest quasar-vite version (2.18.5) yarn create quasar, then added vitest with quasar ext add @quasar/testing-unit-vitest.
When I tried to reference a boot file from my unit tests I got this error:

TypeError: (0 , defineBoot) is not a function
 ❯ src/boot/axios.ts:19:16
     17| const api = axios.create({ baseURL: 'https://api.example.com' });
     18|
     19| export default defineBoot(({ app }) => {
       |                ^

I works if I change import { defineBoot } from '#q-app/wrappers'; by import { defineBoot } from '@quasar/app-vite/wrappers';

[federicobohn-cs]

@IlCallo Im getting same issue. I made a fresh install with latest quasar-vite version (2.18.5) yarn create quasar, then added vitest with quasar ext add @quasar/testing-unit-vitest. When I tried to reference a boot file from my unit tests I got this error:

TypeError: (0 , defineBoot) is not a function
 ❯ src/boot/axios.ts:19:16
     17| const api = axios.create({ baseURL: 'https://api.example.com' });
     18|
     19| export default defineBoot(({ app }) => {
       |                ^

I works if I change import { defineBoot } from '#q-app/wrappers'; by import { defineBoot } from '@quasar/app-vite/wrappers';

@IlCallo I was able to solve it adding alias on vitest.config.mts fille:

resolve: {
      alias: {
        // maps imports from "@quasar/app-vite/wrappers" -> "#q-app/wrappers"
        '#q-app/wrappers': '@quasar/app-vite/wrappers',
      },
    },