Closed blowsie closed 2 years ago
This has been fixed. Wallaby patches some of the filenames at runtime (adding ?wallaby=${timestamp}
) as a part of its runtime / transformation cachebreaker. In the case of unplugin-auto-import
, it could not handle filenames ending with ?=wallaby
suffix and would never add the auto-imports.
This has been fixed in Wallaby core v1.0.1291
.
Issue description or question
I'm using wallaby with vitest and vitesse. Vitesse uses auto-importing to import some commonly used code automatically.
The vitest tests are working fine when running
npm run test
but wallaby doesn't appear to be working with the configuration for auto imports, and as a result, they failThis can be reproduced with this repo https://github.com/antfu/vitesse
How can I get the wallaby vite config to resolve the auto imports correctly?
Wallaby diagnostics report