Intellisense not working with @ absolute path in Vue CLI project
See original GitHub issueInfo
- Platform: Win
- Vetur version: 0.22.1
- VS Code version: 1.37.0
Problem
For projects created with Vue CLI, Intellisense in VS Code with Vetur extension is not working with absolute paths.
Reproducible Case
Steps to Reproduce:
- Create a new project using Vue CLI
- Type in any javascript file or <script> section
import HelloWorld from '@/something/something'
- After typing, ‘@/’ Intellisense should prompt us with all available files and directories based on the path. Unfortunately, it is not working at all for absolute paths.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Intellisense not working for absolute paths in vscode with vue ...
I'm having problems trying to make autocomplete to work with a vue cli 3.0 project with javascript for absolute paths starting with @....
Read more >VS Code - Intellisense not working with @ absolute path
Steps to Reproduce: Create a new project using Vue CLI; Type in any javascript file or section. import HelloWorld from '@/something/something'.
Read more >Intellisense not working for absolute paths in vscode with vue ...
Coding example for the question Intellisense not working for absolute paths in vscode with vue cli 3 project, jsconfig gives error-Vue.js.
Read more >Vue CLI — Make the @ sign in import statement have ...
If you use Vue CLI to scaffold a Vue.js Project, you will notice there is the @ sign in the import statement which...
Read more >C/C++ extension FAQ - Visual Studio Code
Use the C/C++: Change Configuration Provider... command to enable any such extension to provide the configurations for IntelliSense. A third option for projects...
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 FreeTop 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
Top GitHub Comments
No, that’s webpack. jsconfig/tsconfig.json are JSON:
Did you follow https://github.com/vuejs/vetur/blob/master/docs/FAQ.md#vetur-cant-recognize-components-imported-using-webpacks-alias?