You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Coming from Vetur + Quasar to Volar + Vite VSCode plugin + Vitesse and I absolutely love how much more stable (and less fussy) this setup is.
With Vetur, we were able to configure settings for where certain config files and directories were (relative to the project), specifically for monorepos.
I'm currently using a pretty standard monorepo + "workspace" setup --> so the Vite plugin in VSCode cannot correctly find my vite.config.ts file or correctly "read" that this is a Vite project (to get the benefit of automatically starting the server, using the embedded browser view, and debug tools...etc).
I've not been able to find source code or documentation for configuring this plugin to work if I have the following monorepo setup.
@antfu - can you point me in the direction of where to start from (in the code)? It might save me just a bit of time navigating the codebase on my own! :) I've never really worked on a VSCode extension before, but I'm happy to try
Coming from
Vetur + Quasar
toVolar + Vite VSCode plugin + Vitesse
and I absolutely love how much more stable (and less fussy) this setup is.With Vetur, we were able to configure settings for where certain config files and directories were (relative to the project), specifically for monorepos.
I'm currently using a pretty standard monorepo + "workspace" setup --> so the Vite plugin in VSCode cannot correctly find my vite.config.ts file or correctly "read" that this is a Vite project (to get the benefit of automatically starting the server, using the embedded browser view, and debug tools...etc).
I've not been able to find source code or documentation for configuring this plugin to work if I have the following monorepo setup.
The text was updated successfully, but these errors were encountered: