How to get VS Code's "Go to definition" to work on auto-imported components? #17047
-
Currently using "Go to definition" on an auto imported components opens up Is this considered an issue with Volar or perhaps it should be solved with a Nuxt extension? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 9 replies
-
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 |
Beta Was this translation helpful? Give feedback.
-
any updates here? |
Beta Was this translation helpful? Give feedback.
-
@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, |
Beta Was this translation helpful? Give feedback.
@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