Oh wait. This will cause the default type-check command to only check the types of the test files. We will have to modify that as well. But I'm not sure how. As they don't supporttsc --build --noEmit.

Argh. There is a bit of a problem here. Type checking with just usingtsconfig.vite.json won't work as the test files include the app's code, &tsc/vue-tsc --build --noEmit is not supported, as that mode relies on .d.ts output files to compile each project separately and type check them agains't each other. This might mean we will need to not usenoEmit and usedeclarationDir/outDir/emitDeclarationOnly to some dedicated directory to run type checking.

Opinions anyone?@sodatea@cexbrayat

I tried swapping the order oftsconfig.app.json &tsconfig.vitest.json intsconfig.json and VS Code decided to usetsconfig.app.json instead. 🤷‍♂️ I still wonder if that's a proper fix or if there is a way to do this properly. e.g. Some variant oftsc --build that does work for only type checking maybe by emitting temporary .d.ts file to some .gitignored folder.

Oh great. The resolution order is flipped between Volar and the builtin tsserver. Volar will prefer the first matching tsconfig, and tsserver the last!