Volar doesn't perform the source file redirect for project references

[segevfiner]

When's importing a file from a project reference, Volar doesn't redirect to the source file for completion, type checking, like the builtin tsserver support does: https://www.typescriptlang.org/tsconfig#disableSourceOfProjectReferenceRedirect. This allows type checking & auto completion, etc. To work in VS Code even before you build the dependent project's .d.ts.

Steps to reproduce

1. Clone https://github.com/segevfiner/vite-issue-1815
2. pnpm i
3. Open the project in VS Code.
4. Open apps/web/src/App.vue, check the offending import line which will warn with

Output file '.../vite-library-test/packages/foo-lib/src/index.d.ts' has not been built from source file '.../vite-library-test/packages/foo-lib/src/index.ts'.ts(6305)

5. Open apps/web/src/main.ts, notice there is no error for the same import there.

P.S. Why do I need https://github.com/segevfiner/vite-issue-1815/blob/229ca43e34e86b4d7bbb14940f7e5b00ca90dc42/apps/web/tsconfig.app.json#L10-L11 shouldn't this be figured out from the dependency between the projects? Is this TypeScript possibly getting confused due to the tsconfig.json not really specifying the actual output paths and them not matching with what Vite outputs?

[segevfiner]

Added a MWE.

[segevfiner]

It might be that Volar just doesn't work with project references properly at all... Weird stuff...

[johnsoncodehk]

It seems to be a troublesome problem, sorry I can't check quickly...

[segevfiner]

This is quite a complex config, I'm trying to create a monorepo project with multiple Vite apps and libs with the best DX I can get. But as always, it is proving a bit difficult. See vitejs/vite#9979

[gustavotoyota]

I think this is related to #1344

[gustavotoyota]

The problem is that Volar seems to be ignoring Declaration Maps (.d.ts.map files) so it doesn't redirect to the source when using Go To Definition. The built-in typescript extension redirects correctly using the .d.ts.map file.

[gustavotoyota]

Actually, the built-in typescript extension doesn't even need the .d.ts.map files to redirect correctly. It just sees that project references are enabled and automatically decides to redirect to the source when the developer uses Go To Definition.

Volar, on the other hand, displays "Cannot find module 'XXX' or its corresponding type declarations." when project references are enabled and it can't find the declaration files. If it can find the declaration files with project references enabled it then goes to the declaration file instead of the source file when the developer uses Go To Definition.

[segevfiner]

That's the source file redirect thing introduced in TS Server 3.7 that I linked in the PR description.

[johnsoncodehk]

"volar.vueserver.noProjectReferences": true seems also fix problem for this repro, if noProjectReferences have any problems please report to #1344.

[segevfiner]

@johnsoncodehk Thia will require generating declaration maps (On disk .d.ts.map files) and keeping them up-to-date, which are not generated by TS by default, nor by Vite, and require running tsc as they are not supported well by many other ts build tools. Project references obviate the need to do so.

[johnsoncodehk]

volar.vueserver.noProjectReferences is a VSCode setting and it only ignore project references for language server as a workaround of #1344, it will not affect tsc behavior.