How to get VS Code's "Go to definition" to work on auto-imported components?

[jf908]

Currently using "Go to definition" on an auto imported components opens up .nuxt\components.d.ts instead of going to the component source file, is there any way to fix this?

Is this considered an issue with Volar or perhaps it should be solved with a Nuxt extension?

[ojvribeiro]

That's one thing on Nuxt that makes me sad, although I love Nuxt. I hope they figure it out how to do a proper go to component definition in the future. Unfortunately, the Go to Definition VSCode extension by @antfu do not seem to work most of the times, and when it works it leaves the components.d.ts file open.

[viracoding]

any updates here?

[cpreston321]

@jf908 @ojvribeiro @viracoding

Hello all please download this vscode ext https://marketplace.visualstudio.com/items?itemName=antfu.goto-alias.

This will help you navigate auto imports. If this helped please marked this as answered!

Thanks,
CP

[Yasso9]

How do you enable takeover mode ?

[AloisSeckar]

Takeover mode has been made obsolete with the release of Vue official few weeks ago. Shouldn't be needed anymore.

[Tenrys]

I feel like this should be pinned, documented or something, because this makes DX quite nicer.

[AnJ-Github]

@AloisSeckar I'm using new Vue official nad components.d.ts still remain open. Since takeover mode has been made obsolete, is there a way to make it work correctly?

And I second @Tenrys that it should be documented somewhere. DX for someone new to Nuxt3 is really terrible at the moment.

[AAAboutajedyne]

Any updates here, I'm using Vue official and component.d.ts still remain open!
Another problem: when I do go back, it redirects me to component.d.ts first, so I need to do go back twice to be able to go back !