Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"Go to definition" doesn't work in .vue files
See original GitHub issueInfo
- Platform: macOS 10.13.3
- Vetur version: 0.11.7
- VS Code version: 1.20.1
Problem
Cmd-clicking (or F12) on a Vue component import statement has no effect. It’s impossible to jump to the file being clicked on.
Reproducible Case
Issue Analytics
- State:
- Created 6 years ago
- Comments:29 (5 by maintainers)
Top Results From Across the Web
Go to definition not working on my project (vue & sass file ...
I have used the plugin Vetur to support the .vue file. There are 2 ways which work well: Open only one project in...
Read more >Go to definition in vue files : r/vscode - Reddit
In a laravel project, when i am coding in a vue js file my go to definition never works.
Read more >Vue.js Vetur - Go To Definition New Feature (Without Sound)
By: Elad CohenSubject: Vue.js Vetur - Go To Definition New Feature (Without Sound)Small demo to show how you can enable go to definition...
Read more >Vue JavaScript Tutorial in Visual Studio Code
Vue JavaScript tutorial showing IntelliSense, debugging, and code navigation support in the Visual Studio Code editor.
Read more >FAQ | Vetur - GitHub Pages
Template Interpolation auto completion does not work. You are running into the same issue as above — not typing return type of computed...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
VSCode is just an editor which is not ready for productivity. You have to waste hours and hours every month to configure and to get things works right and putting plugin pieces to coordinate with harmony. But, by using WebStorm, all these features are out of box. Just give WebStorm a try and you will definitely love it!
We don’t support omitting
.vuefile extension.https://github.com/vuejs/vetur/issues/423#issuecomment-340235722