In previous version of quasar v2 unplugin-auto-import worked and provided imports via d.ts file. Now unplugin-auto-import does not work with quasar, it seems that environment variables get wiped when this plugin is added to vite plugins. Using server: false and client: false do not fix the issue either. When client: false is added, the plugin no longer creates and adds the d.ts file.
This happens in the latest version of quasar cli SPA app and the new beta vite app.
What did you expect to happen?
It is expected that the vite plugin unplugin-auto-import generates and adds the auto imports into a quasar project.
What happened?
In previous version of quasar v2 unplugin-auto-import worked and provided imports via d.ts file. Now unplugin-auto-import does not work with quasar, it seems that environment variables get wiped when this plugin is added to vite plugins. Using server: false and client: false do not fix the issue either. When client: false is added, the plugin no longer creates and adds the d.ts file.
This happens in the latest version of quasar cli SPA app and the new beta vite app.
What did you expect to happen?
It is expected that the vite plugin unplugin-auto-import generates and adds the auto imports into a quasar project.
Reproduction URL
https://stackblitz.com/edit/quasarframework-5qaesd?file=README.md
How to reproduce?
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
Quasar CLI Commands/Configuration (@quasar/cli | @quasar/app-webpack | @quasar/app-vite)
Platforms/Browsers
No response
Quasar info output
No response
Relevant log output
No response
Additional context
No response