No/broken support for declaration maps in takeover mode.

[filimon-danopoulos-stratsys]

I have a typescript project that emits type declarations and declaration maps. When I use takeover mode, "F12" does not take me to source code as defined in the declaration map but rather the .d.ts file. When I use the builtin typescript language service this works as intended.

[gunhaxxor]

I can confirm this behaviour on my end. Seems like a rather important bug to me 🤔

[filimon-danopoulos-stratsys]

It is mostly annoying since take over mode is the preferred (and quite heavily pushed) way of running Volar. It could be argued that is not very pressing since the type definitions work.

[johnsoncodehk]

Can you try "volar.vueserver.noProjectReferences": true? See #1344 (comment)

[filimon-danopoulos-stratsys]

With Volar takeover mode enabled and the setting proposed in .vscode/settings.json it does not not work for me. Tried restarting Volar and VSCode but made no difference.

Not sure if it makes any difference but the .d.ts and corresponding .d.ts.map files are in an npm-package.

[gunhaxxor]

Same here. Unfortunately not working in a monorepo with several typescript projects/packages

[patroza]

same here, really annoying, especially when onboarding new people.
the problem is the same in non take-over mode, when trying to follow links from within .vue files.

[blake-newman]

should be resolved with: volarjs/volar.js#24

[gustavotoyota]

I'm having this problem as well. Is there a workaround I can use right now?
I'm trying to use @blake-newman's solution, but I can't find know to test locally.